besides, spirituality is not a "component", it's a property emergent from brain structure and function, which is basically purely a physical machine.
115 karma · joined October 20, 2024
besides, spirituality is not a "component", it's a property emergent from brain structure and function, which is basically purely a physical machine.
linux phones can't come soon enough ...
your point about the termn "sideloading" is spot on, though. perverting the language is the first step of manipulation: installing software is "sideloading", sharing files is "piracy", legitimate resistance is "terrorism", genocide is "right to defend oneself" ...
to be clear, my point was that where the state has to be managed is more often than not an architectural decision given by the requirements, and the choice of tools should be a consequence of that, not a precondition.
you guys are furiously arguing (and not really listening) about this or that hammer being good enough to treat every problem as a nail, like ssr was the "holy hammer". well, it isn't and not every problem is a nail, and while datastar looks excellent to me i simply would have no use for it if i needed client side logic or state for whatever reason.
btw, i just now did glance at the menu online, i had no idea that this crap i wouldn't dare to call food (unless i were starving) is currently selling in spain. this is a tiny bit depressing but was actually to be expected, and i stand by my statement :-)
personally i keep dependencies at a minimum and are very picky with them, partly because of nr1, but as a general principle. of course if people happily suck in entire trees without supervision just to print ansi colors on the terminal or, as in this case, use fancy aliases for colors then bad things are bound to happen. (tbf tinycolor has one single devDependency, shim-deno-test, which only requires typescript. that should be manageable)
i'll grant you that the js ecosystem is special, partly because the business has traditionally reinforced the notion of it being accessory, superficial and not "serious" development. well, that's just naivety, it is as critical a component as any other. ideally you should even have a security department vetting the dependencies for you.
1- thoroughly and fully analyze any dependency tree you plan to include 2- immediately freeze all its versions 3- never update without very good reason or without repeating 1 and 2
in other words: simply be professional, face logical consequences if you aren't. if you think one package manager is "safer" than others because magic reasons odds are you'll find out the hard way sooner or later.
... i'm gonna make revolutionary claims and grandiose statements like "built for the ai era".
but i wouldn't mind getting back to the internet of the 80/90s where you could easily find more genuine content and less aggregators, replicators, marketeers and clickfarms. if that's "killing the internet" then it couldn't happen soon enough (i guess marketeers will not go away no matter what, that's a given).
the fear of decline of original content doesn't seem serious. much of what there is now is endless regurgitation anyway. while most of the free stuff nowadays is indeed just noise, the most valuable, original and quality stuff is free, has always been, and it's there. people have been contributing interesting stuff for multiple reasons and in multiple ways for decades, and still do; it is just buried under tons of rubbish. i see no reason why they would stop. if anything, a less noisy internet could be an incentive, and if gaps in knowledge form that will be even more reason to share and contribute, and things like stackoverflow will come back once llms become obsolete enough.
extremely? i wouldn't bet on that.
how do you even measure that? books have been around for over a millenium, that's quite resilient. the internet is barely 50 years old. empires have lasted for thousands of years, modern democracies are a bit over a couple of centuries ... young. how do you determine their resilience? i see quite concerning signs of degradation lately, and they might have something to do with that iron law of oligarchy.
> The article cites a few notable counterexamples like Wikipedia.
no, it doesn't? it has a section titled "examples and exceptions", but it doesn't include any real exception (that has been resilient to this day), let alone a 'counterexample'.
> Your post looks like learned helplessness.
yours looks like wishful thinking (and difficulty in parsing the wikipedia)
my take: as a backend developer he was fixated with the idea of having a server no matter what (if your only tool is a hammer, everything looks like a nail), and as go was his main language he just went with that. then he figured out it didn't really have a point, but instead of just translating that simple logic to js he overengineered the whole thing and overcomplicated his design and build process by transpiling to wasm.
there are some bugs, though. i just won a couple of matches at escoba (very nice little game, i hadn't played this for ... decades!) and the game state wasn't properly reset for the next. that's probably the llm ...
otoh, if we do in fact bring about such a reboot then maybe a full cold boot is what's actually in order ... you know, if it didn't work maybe try something different next time.
if you develop closed software for a walled garden then relying on gpl is still possible but a rather contradictory philosophy. i guess the alternative would have been developing all that from scratch, or getting it from elsewhere, likely paying for it, which would have made those costs even more prohibitive ... otoh i really don't understand those prohibitive costs because supplying the object code was all you needed. what were those? lawyers?
rome doesn't pay traitors.
it's sad to see this core principle being increasingly ignored in linux, but i guess that ship sailed a while ago.
then again recruiters might disagree, not that they tend to be very focused anyway.
not really true, mastication isn't practiced to perfection in the wild, which is why you might often see seeds right on the poop. a portion of them get distributed intact.