Windows - pfff, Microsoft charged companies like Dell for an install on computers they didn't even install it on !!!
HN user
jolt42
I think the progession is like 1) Oh, I can break stuff by changing a config value - it doesn't protect me. 2) Oh, I didn't think X would need to be configurable. 3) With code I can colocate the values with the code that uses them - easier to understand, and I can "configure" anything I want. 4) Why are we using configs?
My realization first time with Eclipse/Java.
Odd to include Chapman and not Dylan. Much like leaving out Twain - seems like the defacto choice to me.
yeah, that's the one. Yep it doesn't seem as intended.
I think the one you are calling "figure hands"... if you mean the one where hands are numbers could just use better styling overall. Two colors, different sizes, better choice of font.
But with Clojure and immutable by default, hot reload is a real thing, it sounds like not just on JVM but even among lisps.
I've yet to find a panacea. For example, I thought DRY was, but found its not the case (test scenarios). I've yet to find altruisms past "everything in moderation". If you do choose a style and stick to it though at least it's consistent.
I've feel like AOP is Spring on steroids. Same downside for both IMO.
I didn't carry a cell phone for long enough (I do now) that people looked at me like I was nuts. I viewed a cell phone the same way most people thought of a pager (remember those things?) - for other people's convenience, not mine. If I am talking to someone in the hall, they will answer their phone, like people that call are more important? Thankfully I think people have realized that - some of the time.
"I would have written a shorter letter, but I did not have the time." - Blaise Pascal
Agreed. Wasn't track barefoot back in the day? I mean even shoes are an advantage. Swimming sped up after goggles and swimcaps were accepted. I think it's all just where do you decide to draw the line? I've thought badminton is an odd sport, the shuttlecock is so slow anyone can (normally) play it - it's very inefficient. And don't get me started on equestrian if grandpa can win it then shouldn't the horse get the medal?
Eh, I like MacBooks because they've been bulletproof. Any PC I suspect it might just go kaput whenever it feels like it, except for maybe a ThinkPad, but they cost more than a MacBook.
I suppose you could chalk this up to an oversight. I don't see how Meta gained from this. They've been purposeful about collecting user data and lying about it, eg: 2025 Android Tracking Incident. Shouldn't just be an embarrassment, should be much worse than that.
I like the qualification of "large-ish". When someone says code is not the bottleneck, I assume they work for a large company. To be fair, at a start-up developers think they code at least 4 hours a day, but it never averages that either.
We really want to believe that we can understand everything, yet we know we cannot.
When we have AGI, we'll have self-driving cars. We aren't getting either in a year's time. The need for white-collar jobs in areas will shrink (not disappear), possibly to expand elsewhere.
Yep, really advanced Google searches were never that good. LLM, yeah, it halucinates, it's never spot on but as sure as heck it knows what I'm trying to ask. It doesn't give me arborists if I say something like "list tree searches".
"The universe is rarely so lazy"
That wouldn't prevent the caduceus from being based on the story.
And yet the similarities can't be coincidental. Rod + Snake = Life Saving.
I always assumed what I felt was obvious: Numbers 21:4-9, where God instructs Moses to make a bronze serpent and place it on a pole to heal Israelites dying from poisonous snake bites.
The logical conclusion is to use "a Haskell" typed language that will ensure every path is considered to guard against AI mistakes. OTOH, clojure repl, expressibility, immutability, and data-driven nature has its own advantages. Tacking on malli (runtime type checking) or spec (types/contracts) helps LLMs avoid type problems altogether or at least confront problems during testing.
Sometimes code is the bottleneck, other times it's not. Large company, not a bottleneck, fixing bugs or individual app developer, more so.
I wonder if Rust becomes more popular with AI as Rust can help catch what AI misses, but then if that's the case then what about Haskell, or Lean, or?
I'll propose this as the only unbreakable law: "everything in moderation", which I feel implies any law is breakable, which now this is sounding like the barber's paradox. What else does anyone propose as unbreakable?
It's easy to chalk it up to "fear of the unknown", when in reality it's both good and bad depending on who's wielding it. It can be used to tear down or build up, solve problem or create problems just like every advance before it. So while I'm generally excited with where it can go, I guess I don't mind being reminded there can be downsides.
Anecdotally, I was just there and ran into a couple of anti-AI people and it's not like I was bringing it up. All I got was they were worried about the water and the heat produced. I wonder if someone has done an analysis of old-search vs AI-search, I most definitely get the info quicker that I want with AI, does that make up for the LLM cost, I have no idea.
Ridiculous? Tandy (leather originally) became a large computer company for a while. So who's to say really.
Why? Is it just not put caramel coloring in it? It didn't taste like actual Pepsi to me, which I suppose might be more difficult?