Clojure is hands-down the best programming language I've used.
That said, I'm still holding out hope that it'll be hosted on top of something other than the JVM -- frankly, the JVM keeps me from using it more than I otherwise would.
I can't help but wonder if this is in any way motivated by the fact that ENS could be viewed as a threat/competitive in a hypothetical future where web3 becomes more mainstream.
Regardless of how you feel about "web3", I think most people (especially in technology) should see this as a problem and aspire to a brighter future where governments/corporations aren't making decisions about what people can and can't see on the web, especially when they're inherently biased.
To be fair, I think this is mainly aimed at developers (and ETH ecosystem developers specifically).
While I don't disagree that there's a "vocabulary" problem (e.g. "dank-sharding"), in a perfect world, a normie would largely just interact with an application without needing to know any of this.
Why do we need bacon? I just want the mushrooms without paying an arm and a leg!
For context, I live in the city and don't have a reliable way (or space) to grow them myself, or else I would.
I'll be honest, these kinds of skeuomorphic alt-meats never make sense to me. That said, I'm someone who eats healthy by default and doesn't consume a lot of meat, so I understand that I'm not the target audience.
But if you think someone living in rural America and eating bacon regularly is going to convert to this stuff, you're kidding yourself.
To add: in addition to fees being used to thwart spam, EIP-1559 introduced a mechanism where these fees (not the block reward of course) are burned. One way to think of it is almost like a "stock buyback" from the Ethereum network: by reducing the supply, your ETH is worth more.
Thus, between EIP-1559 (burns base fees) and The Merge's move to Proof of Stake (a dramatically reduced block reward), there's very little net-new ETH being introduced into the system.
> If the costs to run a validator are too expensive or need too many resources then you just end up promoting a centralized solution.
If I recall correctly, the current number (32) was picked somewhat arbitrarily because, at least at the time, it was "enough" without being "too much" (in terms of incentives, skin in the game, and penalties for bad behavior).
I'd have to use a Googly device to find the price of Ether at the time when this decision was made, but I'm pretty sure it was a lot less than it was now. And once it'd been put into effect, it's difficult (e.g. unfair) to change it.
Longer-term, it likely won't remain so high, especially as the price of ETH appreciates. I believe I recall seeing discussions of changing this number in the future, but it's not the nearest-term priority.
For now, there are decent options around staking pools. Lido is the elephant in the room, but more and more people have been moving to Rocket Pool because it better promotes decentralization.
In the short-term, it's likely already priced in: folks have known this is coming for a while, and especially over the past 2-3 months where it became "real" versus "coming soon".
Longer term, there may be uses for GPUs when it comes to zero-knowledge proofs (think: expensive to produce, easy to verify), but we still have a ways to go in that department.
It depends on a host of factors, so it's hard to predict exactly.
As an example: it depends on the rate at which existing Proof of Work miners move the chain forward. We can make an estimated guess based on the current hash rate, but miners may begin to drop off early and try to "beat the rush" to sell their used hardware before everyone else, so the hash rate could drop more than anticipated.
For what it's worth, my "dumpster fire" comment encompassed far more than just window management (and admittedly extended to Apple hardware and Apple the company). See my comments elsewhere in the thread if you're curious!
Re window management specifically: your "it's not the same" comment are my exact sentiments!
Even if you can hack together some other MacOS-specific window management solution, what I'm finding game-changing is my laptop and my desktop behaving in the exact same way (same OS, same dotfiles, same programs/bins/utils).
Not only "behaving" in the same way, but also configured in the same way (meaning I don't have to maintain two separate configurations for two entirely different managers).
I don't know, I realize my perspective isn't shared by everyone (and even the HN audience specifically), but I'll probably never go back to using a laptop without Linux on it. For a long time, I avoided going down that path because I knew how big of a PITA getting laptop device/drivers to work was (whereas it's generally far simpler on desktop), but that's become less and less the case over the years, to the point that I spend less time configuring Linux than I do overriding all of MacOS's default settings/configuration.
EDIT: I should point out that, although I don't like MacOS, I ditched Apple-related products first and foremost because of both the hardware itself and the company.
Every Apple product I've owned has failed in some spectacular way, and Apple's response is typically something along the lines of "You're SoL dude, you can either recycle it and buy a new product, or you can pay us something close to the value of the device to repair it" (because they solder everything unnecessarily).
Framework finally came along and showed that you can have a sleek, elegant (and modular!) design without soldering everything together in the name of reducing weight by 0.01kg or whatever (or making it a hair-width thinner).
Most recently, I had a 2019 Macbook Pro ($3K) that would frequently give me a "red screen of death" under load and crap out completely.
Before that, a brand new 2018 Macbook Pro I bought (for nearly $3K mind you) became unusable within an hour after taking it out of the box because of the faulty keyboard (several keys either didn't register key presses, or they would turn one key press into multiple occurrences of the same letter).
Before that, I had a Thunderbolt Display ($1K) that would fail intermittently, and it took 5 trips to the Apple store before they finally gave me a new one.
Before that, I had a 2014 Macbook Pro for which the screen started peeling off -- I had to buy a matte screen protector to even be able to see the screen.
I have several more examples as I go back in time further, but you get the gist! In all cases, they're widely known problems that Apple refuses to acknowledge, and assuming they're even willing to do anything about it, they want you to hand over your laptop to them for ~2 weeks in the meantime.
---
Original response:
I'll eventually get around to writing a blog post about this (tm) and HN isn't really the place to fully brain dump, but off of the top of my head, here's a few examples:
- My ".osx" dotfiles (then, now ".macos") would break with every OS upgrade. As an example, I preferred to set a very fast key repeat with a very short delay, and I remember one version of OSX/MacOS that just decided to start ignoring that completely (or resetting it every restart or something, I forget).
- As a TL;DR point that summarizes many frustrations, I'd end up changing almost all of the default settings, to the point that I realized that I wasn't their target customer. For instance, I'd promptly disable all of their elaborate transitions and animations (which effectively added a latency to interacting with the system), hide the dock in perpetuity, etc etc... I haven't used MacOS in a few years, so I'm unable to refresh myself on what else I would change.
- Their window management is SO stupid (IMHO), especially once you start incorporating monitors.
- At least historically (unsure now), there was no way to differentiate the scroll behavior with the trackpad vs an external mouse. I did like the "natural" scrolling or whatever, as it felt very intuitive having used smartphones for many years. However, any time I connected a wireless mouse (primarily for gaming), it'd behave the same way (completely unintuitive), and there was no way to change it to be different. So I'd then have to either design for the least common denominator ("scrollwheel behavior"), or change that setting every single time I used an external mouse and remember to revert it when I'm done. A small nit, but one of tens of examples of annoyances.
I could go on, but like I mentioned, this isn't really the place! Just a few examples as a taste :)