Interesting, and this kind of service seems fine to you? It doesn’t seem fine to me.
Even if most people will have no problem with them, I’d say that knowing how a company handles edge cases like this is much more valuable than knowing how the handle things when everything is fine.
I recently transferred all my domains and cancelled a DNSimple account I’ve had for more than a decade for similar reasons.
A couple years ago they migrated me to a more expensive plan with no notice, I had to catch the price difference on an invoice. I wasn’t happy but it’s a lot of work to transfer domains.
Recently I discovered they introduced a plan that fit my usage and cost 50% less, but (would you believe it) they didn’t bother quietly migrating me to that plan…
You may be interested in Groupcache's method for filling caches, it solves the same problem that I believe this project is aimed at.
Groupcache has a similar goal of limiting the number of fetches required to fill a cache key to one—regardless of the number of concurrent requests for that key—but it doesn't try to speculatively fetch data, it just coordinates fetching so that all the routines attempting to query the same key make one fetch between them and share the same result.
hey thank you for sharing this. Based on what I understand, this package focuses on the underlying storage mechanism itself rather than helping with the cache strategy. It seems like a solid storage extension which can be used Pocache!
> You'll notice I added four "food" emojis: the crab, shrimp, squid, and lobster. I have no idea why they were assigned "food-marine" instead of "animal-marine". They look happy, healthy, and uncooked.
On Apple platforms, at least, all the crustaceans mentioned are red and therefore look very much cooked.
He's lucky to be able to do it more than once. A friend's cousin got acute reaction from pathogens in raw fish which got him to ICU and now the doctor said he should avoid eating even cooked fish because he could do an allergic reaction.
Hmm. I was excited about Zed, but it now seems painfully clear they’re headed in a completely different direction than I’m interested in. Back to neovim, I guess…
The author seems to imply, as if it were generally understood and accepted, that the reason nuclear reactors are heavily regulated is because they produce a lot of energy.
Perhaps that's a component, but one really doesn't need to think about it too hard to identify better explanations for why this particular energy source is held to unusually high regulatory standards.
I don't have an opinion as to whether other large-scale sources of energy should be held to similar standards, but to suggest that solar energy's failure modes are comparable to nuclear energy seems intentionally misleading.
> In the Netherlands alone, these solar panels generate a power output equivalent to at least 25 medium sized nuclear power plants.
> Because everything runs through the manufacturer, they are able to turn all panels on and off. Or install software on the inverters so that the wrong current flows into the grid. Now, a manufacturer won’t do this intentionally, but it is easy enough to mess this up.
> As an interim step, we might need to demand that control panels stick to providing pretty graphs, and make it impossible to remotely switch panels/loaders/batteries on or off.
Basically, if a hacker were to make all batteries (or panels) suddenly switch between full discharge and full charge every second or so, it would tear down the electric grid. Voltage and frequency would swing rapidly, and whatever plants are riding load would struggle.
This could create a massive power outage; but there is a huge risk that this could damage power plants and other infrastructure.
I’ve also recently switched (largely) from Vim to Zed and I also think that Zed is in many ways great.
At the same time it’s been pretty frustrating to use an editor that is spending so much time building AI integrations, REPLs, and so fourth when basic things like cut and paste and common Vim motions still have so many bugs.
I’d love to see them prioritize getting the basics solid first.
Yeah I feel the same way. The fact that Zed uses the system clipboard as the default register in vim mode, for instance, made it impossible to use in practice for me -- having every yank replace my clipboard was a bit of a nightmare!
The `+` register is the system clipboard in vim already. What you're referring to is remapping the `+` register as the default register (in place of the 'unnamed' register, which is accessed explicitly as the `"` register) for some operations - typically yank and paste.
I don’t know. That feels perfectly reasonable for what I imagine is 99% of all developers, so while sad, I can imagine why that use case is not very high on their list of priorities.
> That feels perfectly reasonable for what I imagine is 99% of all developers, so while sad, I can imagine why that use case is not very high on their list of priorities.
I think you might be under the impression that what the GP is complaining about is having the default copy and paste go to the system clipboard.
This is not what is happening; in Vim all modifications are saved to the default register. Making the default register the system clipboard is annoying, because the following happens:
Insert a newline? Newline replaces whatever is in the clipboard.
Switch around two letters in a typo with `xp`? That text replaces the contents of the system clipboard.
Remove a word? Change a word? Add a new word? All replace the contents of the system clipboard.
Run a macro that changes things around? Nukes the system clipboard.
I don't think that 99% of developers want this behaviour. What they want is that when they explicitly copy something, it must be reflected in the system clipboard.
I assume all of these are some special combination of keys/modifiers? While I agree it’s less than ideal, at least you always know it’s going to happen if you are sort of familiar with Vim.
> I assume all of these are some special combination of keys/modifiers?
It's rare, in Vim, to not use commands. It is, after all, a command-oriented interface.
Any command that removes text or modifies text places the removed text into the default register.
> While I agree it’s less than ideal, at least you always know it’s going to happen if you are sort of familiar with Vim.
The problem with making the default register nuke the system clipboard is that almost all text editing commands are going to nuke the system clipboard.
To be frank I don’t the majority of us care about these collaboration features. We just want a way to write code that is performant but makes it easy to leverage existing language servers.
I want to pay for Zed for what it is. I want to sponsor a new code editor. I have zero interest in paying for a SaaS collaborative editor.
Given that the unemployment rate in the US (at least) is still extremely low (about 3.5%), it’s at least worth considering that if the people working gig jobs wanted full or part-time employment, with the set of trade offs that entails, it’s probably available to them.
I live in New York, but I rarely go to hotel bars here because, while frequently comfortable, they are outrageously expensive. On my most recent visit this spring I paid $24 for a single very mediocre cocktail.
Hotel bars are in a liminal space where some of the best bars in the world are in big city hotels, but also some of the most disappointing bars. Hard to know without searching in advanced. I'm not sure I would just walk in when the prices are steep across the board for hotel bars.
Even if most people will have no problem with them, I’d say that knowing how a company handles edge cases like this is much more valuable than knowing how the handle things when everything is fine.