only under the assumption that the governments job is to contravene the law of the land - which up until pretty recently no one believed including the government
not a lawyer, but I believe the process involves (a) deciding if there is a case at all to be argued, which is this case there clearly is, and (b) weighing the harm of letting the government send US citizens to Sudan or life in prison in El Salvador vs the harm that would be caused by preventing the government from doing that while the case is adjudicated - which seems to be nonexistent.
That last point is where we disagree. It takes many years for a case to wend its way through the courts. We're looking at a world where a relative handful of lower court justices can issue injunctions one after the other until it's impossible for the president to do his job.
There's only one court that has the authority to issue nationwide injunctions, and that's the Supreme Court.
Ah, this is what happens when one dredges up old knowledge and doesn't seek an updated understanding before sharing. Thanks for the correction on the colloquial classification.
presumably that in HPC you can dump enough money into individual users to make the platform useful in a way that is impossible in a more horizontal market. in HPC it used to be fairly common to get one of only 5 machines with processor architecture that had never existed before, dump a bunch of energy into making it work for you, and then throw it all out in 6 years.
so much of programming has been shaped by fads than I don't think you can safely point the finger at 'everything is a dsl' as being a root cause. back when lisp was really being put out to pasture, it seemed like the major complaints were about performance and syntax. and how if it wasn't object oriented then it really belonged in the dustbin (of course ignoring clos and the mop)
I'm sure of that but it seems that LISPs being too flexible hurt their adoption rate somewhat and the mainstream preferred to have more guardrails on their programming languages. Ultimately developers are the ones who decide what they like and popularity quite often reflects what's being done commercially. I agree about the fads part.
flexibility didn't reduce adoption : lack of expectation did. once a language stops assuming the user will change it, the culture settles into consumption. lisp didn't ask permission to be rewritten, most modern stacks do
if I pay a bunch of employees to take the cloth I buy and cut and sew into shirts, that's an expense some directly out of my revenue and isn't taxed as profit or forced to be amortized. Why should software be different?
this is one of the most depressing things about recent turns. this directly manufactured outrage. these petty dramas, this US govt a tv show. Oh no, did you see what trump did to that foreign leader? we've been explicitly given a sham, playacting government whose primary mission to be replace honest debate with this sham soap opera. i expect soon to found out that the Elon that we see is really his secret twin.
you're right. but the ability, given a good idea, to spit out a substantial amount of code that compiles and basically runs in a single session removes alot of the consternation and back and forth in those discussions
despite industry motion to the contrary, the truth is that we really can build anything we want. if we just weren't such cowards about it
Do you find that typos are the biggest barrier to quickly writing code that compiles and runs in a single session? I'm an absolutely _atrocious_ typer (in terms of both speed and accuracy), and yet I still genuinely don't think that actual typing takes within an order of magnitude of the time it takes me to get out a quick prototype compared to debugging.
doesn’t have to be a legal enforcement if vendors just don’t work with bodies that insist on this counterproductive notion of standards as a profit center.
unfortunately i think there us some degree of collusion here. it’s easier to get your existing proprietary standards ratified if there are fewer players in the room and the palms that need to be greased are clearly marked
It's not exactly clear cut. Standards are unfortunately in general quite expensive to produce and maintain.
Software oriented standards are certainly cheaper than metallurgy, machining, manufacturing, building construction, environmental, health & safety, and the other big classes of standards however they still have quite a cost.
Historically the ISO standards development process for software standards (like the C or C++ standards) happened only in small part asynchronously and historically required large, extended-duration committee meetings where all the details were hashed out in person. This process only really started to change during COVID but even then it's still a very in-person synch-heavy process and that's not exactly cheap to run.
And with most standards, the FDIS (final draft international standard) revisions are made public. They can be found online even if they can be annoying to dig up. For 99% of cases the FDIS revision is more than sufficient and is identical to the published standard minus a typo or grammar mistake here and there.
As the average SW dev or engineer of course you don't need to fork over the cost for the published standard but any large company will probably purchase a catalog of standards rather than deal with the overhead of dealing with FDIS (and any legal risk from not following the "true" standard).
It is also worth noting that pretty much every university library (and many public non-university libraries) has some contract or service that provides access to copies of the standard to members free of cost.
- https://github.com/EbookFoundation/free-programming-books/is... -- "The most recent freely available draft of C17/C18 used to be c17_updated_proposed_fdis.pdf, but it's no longer available directly and you need to use Wayback Machine to download it."
- I used to work for a multinational software company whose bread-and-butter was C. The company had indeed purchased a catalog of standards, but that catalog didn't include ISO C. When I formally proposed just that, they rejected it (and kind of made me feel uncomfortable about my proposal, to boot).
I used to work in standards. my organization supported my salary, my travel, and paid membership fees. yes, the standards body did rent the hotel ballroom, and run a website. but otherwise the task of making the sausage was all volunteer.
you can build these without shared memory using standard distributed database techniques for serializability and fault tolerance. i dont think its a particularly good idea. there's nothing great about running 'ps' and getting half a million entries. using the unix user/group model isn't great for managing resources. its not even that great to log in to start jobs. the only thing your gaining is familiarity.
building better abstractions - kuberenetes is an example, although i certainly hope we dont keep being stuck there - is probably a better use of time
reply