I guess what I'm suggesting is it should be available over the counter, but not off the shelf.
2,340 karma · joined January 3, 2019
I guess what I'm suggesting is it should be available over the counter, but not off the shelf.
The fraction of businesses that need something really custom/special is vanishingly small. And the fraction of businesses that need a pixel-perfect design and consistency across all their pages is tiny, too. Your customers don't care about that crap nearly as much as you do. Just keep it simple and make the information they're looking for easy to find.
I'm a software engineer. I love building stuff. I can make kick-ass web stuff if called upon to do so. But please, don't waste your money paying me to build something you don't need.
Also, I thought I recognised your username. I use at least one of your crates. Thanks for those, too! :)
Sure, I have to take some responsibility for poor digital hygiene or whatever, but I don't think that negates Google's awful management of this. I shouldn't _have_ to be vigilant/proactive to stay safe in something as basic as this.
Aside: Google spams me with all kinds of noise in notifications these days; couldn't they at very least put something in there saying "by the way, your device is now EOL; buy a new one"? Ockham's razor suggests to me that a _lot_ of people are running unsupported devices still, and Google doesn't want the collective backlash of putting that uncomfortable reality in people's faces.
Every year I'm more disappointed by Google on pretty much every front. They really do seem to have jumped the shark.
If I do decide to upgrade...
Unfortunately I can't stand iOS. No kidding, I'd rather have a Nokia 5110. I've tried repeatedly, thinking "I'm just not used to it", but there's too much about the design philosophy that I find actively obnoxious. Strangely, I don't have this problem with macOS.
Maybe I can find another Android vendor with a better support policy, or if none of them are any good then just suck it up and buy the very newest of whatever to at least push the planned death of my device back a couple more years.
I'm getting a bit sick of this treadmill. I don't buy the defence some people offer that it's too much work to support the older devices. Having a security-only backports release series for old devices would be _trivial_ compared to the enormous piles of money Google sets on fire for shits and giggles on a daily basis. It's planned obsolescence, plain and simple.
That's not really the same thing as "updates for at least 5 years". The date the device first went on sale in the US isn't particularly relevant. They'll still sell it to you long after that, and then end support not long after it's out of warranty. That's what happened to mine.
The lessons I'm learning here (if I'm running a first party OS) are:
- Check very carefully how long different vendors actually support their devices. Google is pretty rubbish on this front, it turns out.
- Always buy the latest model when buying a new phone, even if it doesn't have anything I need, or I'll just have to "upgrade" twice as frequently instead.
(Yes, I know: get a better ad blocker, etc. — I'd rather have fewer weak links, though, and a lack of basic OS updates is a pretty big weak link.)
Personally, or at work? Personally, the first steps are actually pretty easy: install an operating system that doesn't do this stuff. And then deal with the fallout as best you can without going back — e.g. finding replacements for software that only ran on $OTHER_OS. Source: did it decades ago. No regrets.
At work? Good luck. We have no credible professional bodies that enough workers are involved in for them to have much relevance, and employers that actually have any kind of values relevant to this discussion are vanishingly rare.
I think the most productive thing would be to start conversations about ethical choices in the computing professions. Start local (friends, colleagues, local meet-ups). Find existing groups with similar values, and share experiences. Then _federate_. Set up regular inter-group meet-ups. Over time, formalise a union out of the federation.
Edit: oh, and don't be an extremist. Keep your policies lean and well within the Overton window. Pick your battles carefully. Compromise isn't weakness — it's just realistic. As long as you're moving things in the right direction, it's still good.
(I don't have any strong opinions on it personally, because I'm not invested in that particular ecosystem. I'm merely attempting to distil what I've heard from other people.)
My greatest practical frustration from this is the difficulty of trying to claw back performance when it becomes important. I'd like more ways to say "from this point on, none of X, Y, or Z will change", and get some performance guarantees in return. For example, we have some code that dynamically generates a whole lot of classes from protobuf definitions. It's bad enough that it takes nearly a minute just to load an run all that code, but even after that I'm paying the cost of assuming that any of those definitions might change at any moment. So I have awful load times, and awful runtime performance.
I guess what I'm asking is: do you see a future where there is more explicit control afforded to people who want to pick their own tradeoffs without resorting to writing everything performance-sensitive in extensions written in C/Rust/whatever?
What should I be buying to not have to ask myself that question?
(BTW, I'm deliberately avoiding making any distinction between so-called "true random" and PRNG above, because the difference isn't actually meaningful here!)
Especially now that this has been on Hacker News, I don't think even Microsoft is stupid enough to go on the offensive over something like this. The bad press would be so much greater than anything they have to gain.
1. Send a lot of people (15?) and give people some flexibility in who they spend time with. 2. Give people a lot of space. I mean a _lot_ more than you think you need. Inflatable habs could be one approach, but if Starship gets going we might not even need that. 3. Let people escape. Loads of video games, books, creative projects, etc. 4. Help people anticipate the destination. Include remote control (obviously not real time) of robots at the landing site as one of the ongoing training exercises. Regularly simulate missions you'll be undertaking on the surface. 5. Give people lots of space at the destination. Cut and cover enormous living areas, and let people customise them. Give the crew something to look forward to.
People survive worse, and some people are better suited to it than others. We'll start by sending the people who are expected to fare best.
I suppose I am just some random on the internet, but I think a lot of people unjustifiably think "human factors" are insurmountable. Yes, it'll be hard, but the kind of people who plan these missions are used to solving hard problems.
Mars is disconnected from Earth's biosphere. To most people, we wouldn't be ruining anything ecologically important or otherwise sacred by colonising it and bending it to our needs.
The Mars-Antarctica connection isn't particularly strong.
Context: I've been thinking about this recently whenever something to do with machine-written music comes up. My best attempt to describe what music is to me is something like "the patterned construction and resolution of rhythmic and tonal dissonance" — i.e. start neutral, create something that feels slightly uncomfortable, but hint through the pattern how it might be resolved to make you comfortable again. Kinda like storytelling, come to think of it.
So what if instead of a series of Sierpinski triangles, you used hailstone sequences, or anything else that contains interesting complexity and eventually returns to the origin. Could you mix and match different filters ("reject anything that doesn't fit this equality") and maps ("natural numbers to pentatonic scale", "natural numbers to commonly used chord progression"), and then apply them recursively? Could you end up with something that people would interpret as "real music", or would it always still sound like obviously computer generated "not-quite-music"?
What could be done about that aside from expecting people to just... be better? I think the shape of these forums induces those kinds of comments, even if the community and moderators make a real effort to uphold higher standards. And I think if I encountered the same people in a different kind of forum then I might have a higher quality conversation. Heck, my own comments would probably be a lot more constructive!
Real world example of what I'm thinking: I have a neighbor over one fence who has very different political views to mine. We have perfectly civil conversations in which we're both actually really engaged and trying to understand each others' perspectives and experiences, and not just keeping the peace by avoiding difficult topics. It feels like effort we put into the conversation is rewarded.
I can't shake the idea that there might be "one weird trick" (okay, maybe a handful used together) that could make it more rewarding to put more effort into online conversations on forums like Hacker News or Reddit. One I've wanted to try for a while is to recreate something along the lines of Slashdot's moderation system, but with room for a meta-conversation to take place in "moderation space" (in which all community members could participate) and for there to be opportunities for people to refine their comments in response to feedback — and for doing so to be the norm.
Maybe it's not that simple. That's okay, too. But I've seen different moderation strategies around the web produce very different results, so it seems to me that there should be plenty of room for experimentation, and a lot to learn from doing so.
That was a wild time. Nobody talked about security back then. The idea that everything in our lives would eventually run over the internet just wasn't on people's minds.
Yep, that is a great takeaway. Another important example is GCP pricing, and their habit of killing off products and services as fast as they build them.
What Google is doing or charging today is not a reliable indicator of what they will be doing or charging tomorrow. AWS may have its own problems, but at least they don't do much bait-and-switch pricing, and they tend to support services for a while after they launch them.
It _should_ be useless (for some reasonable definition of "should") — it just isn't in practice. And I'm continually amazed at how often people confuse one for the other, across all contexts. E.g. I have family members who refuse to consider that our justice system might have deep flaws, because to their mind if it should be some other way then it already would be.
- Switching away from an M1 MacBook because they can't stand macOS.
- Happy with Windows or Linux from past experience.
- Close lid, put in bag is an important workflow.
- Something reasonably modern and capable would be nice, but doesn't need to be a powerhouse (don't need current gen CPU necessarily, don't need discrete graphics).
Does anything on the market actually have reliable power management? I've been looking at the Dell XPS range, Lenovo Yoga, X1 Carbon, and Framework laptops today. But I can find power management horror stories for all of them, so I don't know what to think.