Basically the most vital role, if you're trying to keep everyone in a Burton Klein Happy Warrior/type-1 mode.
(Which is 0.005% of companies.)
9,514 karma · joined April 20, 2007
(Which is 0.005% of companies.)
I think of getting rid of it but it takes so little time & money to keep around, and it's great being able to do occasional road trips. Otherwise I'd totally get rid of it. Insurance is the biggest cost, but pretty cheap all-in-all.
Given how little it's used, and given what a generally chill driver I am, I do think I deserve a better deal. Then again, it's old & I don't think it has OBD, so I'm probably not eligible anyways.
But yeah, preemptively removing batteries for safety is a good move.
Thankfully with Android I can just plug in a mouse! On my Samsung phones I can plug in a full display + mouse. It's a bit of a risk leaving thr gate open like this, but occasionally I've also setup dying phones to auto switch to ADB, so when they do go, I can still access them.
The main barrier I have is that some phones have bad usb micro ports. With that, I'm hosed. Thankfully haven't seen a single usb-c device with a bad port; loving it.
Ideally we should be able to trust on-disk encryption on our phones. Alas with pin codes, there's not enough entropy to do a for real job of encrypting, but it'll ward off casual snooping. I'm honestly not sure when the changeover was where users ought to be able to expect this fundamental builtin protection.
It's starting to change, but for years people would look at me like I was crazy for running Debian/unstable aka Debian/sid on my machines/personal servers. Being willing to have volatile systems is a big barrier. Only having "dogfood this wip" or "pay us" as the two options is a radical ask, one that doesn't really seem survivable to me (rh/centos won't go away, but their mindshare seems likely to implode to me).
The other bulk of thr market is mobile, which is almost entirely arm already.
If RHEL is only for paying people, as McGrath from the pulpit so expounds, most people are gonna leave. The value was having a community, a good path, that extended from open source to paid support. If McGrath blows up one end of the continuum, the other end will certainly wither collapse & die. This is a deathmark. People are upset to see a vibrant world shut off and thus shut down, whatever the value/greed/whatever of the situation. A pillar of Linux has left the chat.
McGrath seems to be fessing up to removing access to binaries, and has his hard-truth he wants to try to deal, but but it seems like the story goes significantly deeper or the anger/frustration wouldn't be anywhere near as high. It's not clear to me from a quick browse of the repo what backports/security fixes are/aren't available.
You say that prices go up because they can, and that's not wrong, but historically there were other providers also competing. It feels like there has been massive consolidation across industries, and that this centralization has created uncompetitive markets, where consumers don't have any option but to accept a providers price & profit increase.
That feels like the new thing, the new trouble: only the very large are left. Competition does not renew: even if there are fat profit margins waiting to be had, the risk of trying to start a new competitor is too high, too likely to get crushed, has too many personal risks (trying to provide healthcare for your family, not go bankrupt, etc).
The markets have ossified into a state where this ruin you speak is possible.
This should be something hopeful & exciting. But instead of a healthy competitive market, we fund exploitative systems.
It's not even a comprehensive rollout. These stagnant providers receive a ton of money then just fail to roll out. New York for example is back in court over just this, but whether anything ever improves is uncertain.
Regarding AI, I have my doubts buy acknowledge it has remarkable potential for raw output. But how malleable will that output be? Will be make good architectural decisions that allow ongoing adaption & iteration? Will it be able to understand & marshal architecture forward in an intelligent way? I have little evidence yet telling me systems like LLMs are capable of architecting well.
> We were told to stay on top of the most modern ecosystem, and by that I mean dealing with compatibility being broken every two months.
Some people just want to be ornery & cantankerous.
The article can be not wrong about saying there's too much hype, marketing, and rationalizing that we know real answers. Fools with certainty are everywhere. But it can still be wrong & have a jerk attitude. That we still have to figure things out & can be wrong or overadopt is not some horrible flaw. It doesn't mean we can skewer all these ideas & crap on them like this cavalcade of schlock.
So many of these various ideas do keep reoccurring, keep having real use. XML is reborn as jsonld which has some great uses. Isomorphic JS is alive & well in the new server side react craze. GRPC and Kubernetes and dozens of these other techs provide a normative baseline that let many teams work together where before we had anarchy & disorder.
There's some good messages & ideas here. We do need to iterate & refine & assess value. But also this is a conservative paean. A back to the land, just simple code ideology that is so appealing, that let's folks look down their nose & reject assessing technology fairly, that doesn't allow for valid complexity. Rakishly anti-elitist, thinking itself better for being such a smart source of truth only because it can smash other works so effectively. Be more liberal & open minded, not so fixed: accept that most of these things have some really good morsels or kernels that have value
Modern software is a couple decades old. Of course we are still refining & learning. Most of the things here have provided real value & informed where we go next, happened for real reasons. Some will fade, but many of the ideas will reoccur, will be better more creatively worked in or worked together in more cohesive wholes. This is a great amazing process, we happening live, in a young industry. Absolutely, beware of hype & bandwagons & marketing, of anyone who would tell you this is the way. For we don't know, and we have a long road ahead with many unexpected turns to figure out where computing's truest values lie. Stay young, stay hungry, and stay a bit foolish.
I do hope some day we can make computing more visible & honest.
It's a little weird because presumably repos shouldn't just be a .local folder. We'd still be excepting the actual source from this.
Maybe we just use a FileSystem Heirarchy pattern for repos? Many projects already have source in src/. Move all the build config stuff into a etc/ in the project, no .anything/?
This case isn't covered by XDG, but there's a path here we probably could & should adapt, that suggests itself. And this forges off in a new direction.
https://specifications.freedesktop.org/basedir-spec/basedir-...
For a while I was dumping stuff into .config but I eventually tired of struggling even more with various tool chains.
HN is well optimized on mobile. It's great as is. Lot of people just bullying their opinions.
Sounds like that's not yet going to see this fee. Could you imagine what a pain it would be to have a fee like this & have staff around to take the flak for it?
These mechanized economic processes allow companies to put humans at their complete mercy, in a way where no real response is possible. Far off technological control.
> The brain infrastructure that connects neurons is collectively referred to as the cytoskeleton. It includes proteins, neurotransmitters, filaments, microtubules etc. Above, we saw how electric fields generated by neurons and other parts of the cytoskeleton carry information being used for behavior. Here, we propose the Cytoelectric Coupling Hypothesis: Electric fields help organize components of the cytoskeleton in order to "tune" it to process information efficiently.
Stunning complexity.
But above all, it's exactly this that's the biggest problem. I'd wager like 75% of devices have an OpenIPC capable chipset. But there's only rudimentary tracking of what devices have what chipsets.
And it's unknown what other wrinkles folks might run into if they do get a device with a valid chipset. Most should just work, but a number will also require more embedded hacking.
Such an amazing project though. Stunningly wide support for a huge array of chipsets.