I tried some D some time ago, it is a nice language. Given today's landscape of programming languages I think it's difficult to reason why a program should be written in D if there are more programming languages that overlap in features. Also depends on how fast you need to scale in developers, how quickly people can learn a language (and not just the syntax) so popularity is also important. I work in consultancy and this is what I always factor in for a client.
"Home & Garden Television". Lots of shows about flipping houses, etc.
It used to be far more instructional (Julia Child-esque) before it and Food Network got swept up in the reality TV craze. It still has the "bones" of its former self though.
In the Netherlands we return 30% of your taxes in the first 10. So we welcome you as well. We may pay less compared to the USA but we have health care, better work life balance and we all talk English.
From 1 January 2024, expats who meet the conditions receive the following tax benefits:
- 30% tax free for the first 20 months;
- 20% tax free for the next 20 months;
- 10% tax free for the last 20 months.
So that's a tapered reduction over the first 5 years and the amount of money that you gain after tax is between negligeable and insultingly small.
Basically in its current form "The Dutch 30% ruling" is not really worth it, if you want to move to The Netherlands do it for other reasons, and the advertisment of this mechanism feels borderline disingenious in its current form.
I think it was like that some years ago. Now, as you said, it's really useless. 20 months are just the time to find an apartment, furnish it and get used to the place.
Afterwards you have to pay some of the highest taxes in the world....
Dutch people still speak Dutch to each other so if you were going to live there permanently and wanted to properly participate in society you would need to learn Dutch.
However the average level of English ability in NL is extremely good, you won't meet many people who don't have really good English especially for younger generations. Definitely not the case in e.g. France or Italy
Redis still has a niche. For something like a job queue, SQL is probably fine because adding a few ms of latency isn't a big deal. For something like rate-limiting where each layer of microservice/monolith component has their own rate-limit, that can really add up. It's not unheard of for a call to hit 10 downstreams, and a 10ms difference for each is 100ms in latency for the top of the waterfall.
Redis also scales horizontally much, much easier because of the lack of relational schemas. Keys can be owned by a node without any consensus within the cluster beyond which node owns the key. Distributed SQL needs consensus around things like "does the record this foreign key references exist?", which also has to take into account other updates occurring simultaneously.
It's why you see something like Redis caching DB queries pretty often. It's way, way easier to make your Redis cluster 100x as fast than it is to make your DB 100x as fast. I think it's also cheaper in terms of hardware, but I haven't done much beyond napkin math to validate that.
> But I am not a storage/backend engineer, so maybe I don't understand the target use of Redis.
We use it to broadcast messages across horizontally scaled services.
Works fine, probably a better tool out there for the job with better delivery guarantees, but the decision was taken many years ago, and no point in changing something that just works.
It's also language agnostic, which really helps.
We use ElasticCache (Valkey i suppose), so most of the articles points are moot for our use.
Were we to implement it from scratch today, we might look for better delivery guarantees, or we might just use what we already know works.
You'll be amazed on what the new breed of engineers are using Redis for. I personally saw an entire backend database using Redis with RDB+AOF on. If you redis-cli into the server, you can't understand anything because you need to know the schema to make sense of it all.
I love the idea of PG for everything, but every time I suggest it I get the same answer "When you're a hammer, everything looks like a nail" which makes sense to me, but not sure how to give a good answer to that phrase :(
I mean, that's just a truism - it's not really engineering advice. Maybe Postgres is just a hammer, but when you're building a house there's a lot of nails.
If you've got to store 5 GB videos, maybe reach for object store instead of postgres. But for most uses postgres is a solid choice.
I loved Blacklight Retribution. It's been so long delisted that my most unique achievements from it disappeared from my profile. One was 0.01% of all players.
It's surprising that it doesn't seem like the X-ray mechanic (which is the main thing I remember from that game) was really picked up by any other game. There were way fewer cheating accusations than in other games, because what would normally be a "cheat" was a core game mechanic, and IMO that made it really enjoyable. It's a shame that game died.
There is a fan project that has revived the servers. It’s hard to get full matches but can still be played at least. It’s called BLRevive, there’s a Discord for it. IMO the only bad thing is it’s based on the post-PS4 update where the devs console-fied the game.
Well HDMI is better than all the standards I used before it. Never did something with DisplayPort but for what I can tell it's Apple related (right?). I used DVI-I, DVI-D, VGA, and even old stuff in the past.
There is the vesa standards organization with a pretty good history of successful display connections standards vga(analog video) dvi(digital video) and displayport(packet video) and very little drama affecting the end user with how the connection is used.
Contrast this with the hdmi consortium which put together the hdmi standard. originally hdmi was just dvi with a built in audio channel. and while I will concede that the audio channel was a killer feature and resulted in the huge success of hdmi. They really did very little technical work and what work they did do was end user hostile (hdcp rights management)
It really is too bad that display-port is sort of relegated to computer monitors as it is better designed and less end user hostile than hdmi. but hdmi with it's built in audio channel won the market for digital video connections and by the time display port was out people were, understandably, reluctant to switch again. While display port is better, it is not enough better to be for the end user to care.
Have you even bothered reading any discussion here? I can't downvote you but its easy to see why others did so, a very lazy and clueless comment about very basic of tech everybody uses, on Hacker news. You can for sure do better.
yeah I still have my old Panasonic SL-SX410 from 1999 or so, barely larger than the CD itself and with included AAA rechargeable NiMH batteries - kind of special at the time and it would charge the batteries itself (no separate charging station needed). I actually still have the original batteries and they still hold a very small charge. Maybe can listen to one or two songs lol
Yeah! and check out that little "remote", allowing quick access to pause/play/skip and volume control! I could just keep the CD player in my pocket and be walking and listening to music, never needing to take it out of my pocket basically. Super cool :)
Would love to work on a project with this as a rule but I am working on a project that was build before me with 1.2 million lines of code, 15 years old, really old frameworks; I don't think we could add features if we did this.
Same. The legacy project that powers all of our revenue-making projects at work is a gargantuan hulking php monster of the worst code I’ve ever seen.
A lot of the internal behaviors ARE bugs that have been worked around, and become part of the arbitrary piles of logic that somehow serve customer needs. My own understanding of bugs in general has definitely changed.
reply