zelly

Big problem with the field of biology, like Peter Thiel says, is it's the science field people go into to avoid math.

Of course it's when I actually need to use it that it goes down. I'm now researching how to transfer the domain to Route53.

The apes have run out of shapes.

Run your own DNS server locally. It's not that hard.

He should be complaining to the standards bodies. DKIM keys should expire like most other asymmetric cryptosystems. There will always need to be backward compatibility, but then it's your fault if you're using outdated software or not using a major mail provider (who would very certainly support the new standard). Directing this complaint to one company seems bizarre because most people who care about this kind of thing aren't using Gmail to begin with.

Super secret spy agencies are much less competent than you'd be led to believe. I'd be more afraid of Google and Facebook.

Linux UI is far worse than Windows. It's not even close. I use Linux but definitely not for its UI.

Windows can out-of-the-box do HiDPI, multiple monitors, multiple desktops, trackpad gestures, hardware accelerated UI rendering, facial recognition logins, and more. It was designed as a desktop OS.

On Linux some things are getting better if you stick to the Wayland+GNOME stack, but it's still so bad I can't recommend it to people on technical grounds. Use it if you believe in free software, not because you think it's "better" (it's not).

Then you don't get to use what is probably the biggest selling point of MBPs, their patented touchpad and gestures.

Still waiting for a built-in debugger like IDA has

Battery is not so important post-covid.

Air is clearly the better value option, if you really want to get one of these.

If Apple is so good at chip design why don't they just pivot to that? Then we can all standardize on the single (objectively superior) software stack that is Android. There is a lot of money to be made with licensing and they wouldn't need to run a huge supply chain anymore. It doesn't seem right that the best architecture in the world is locked in to a very specific ecosystem when the whole world could be benefiting from their innovations.

The overhead of Kubernetes's runtime (Go) is nonzero. It's meant to run on Xenons which is going too far for a home server. You have the slow Go GC then you add on top of it a bunch of PHP and Ruby apps like Nextcloud, sprinkle a bit of unnecessary virtualization, and you've got a really slow machine that burns through more money on your electric bill than an equivalent EC2 would cost.

Since everything I use at home is Linux, they're all "servers" already. They're all on a Wireguard network and share NFS mounts that I can access anywhere. No PHP, No Letsencrypt certificates, No Docker, No Kubernetes, No wasting electricity, No fiddling, No "git commiting every edit". My setup works just as well in a house with a static IP from an ISP as it could in a van with an antenna receiving 4G data.

Where's the Rust Django? Is this false advertising?

Ten years ago it looked like that might be where the entertainment industry was headed, but then Netflix and Spotify got big because it was even more convenient than torrents. When there are 10 major streaming services with exclusive content, then it's no longer convenient and torrents come back. If it were stupid-easy to get torrented content on a big screen television, then Netflix et al would be in trouble. That's the one missing part, which may keep people on streaming even with the Tower of Babel variety of different services. Netflix et al is installed by default on all new TVs you can buy in a store now. I think there was an attempt to make pirated content easy to consume, those Kodi boxes which are now banned and relegated to enthusiasts now. That's what they are really afraid of, because when your mom can torrent with a remote control it's over.

(Spotify on the other hand is in a different league because there is almost no such thing as exclusive music. It's still way more convenient and time-efficient than torrenting. In my experience you can't even find music torrents anymore unless you go down the private tracker rabbit hole (which definitely doesn't scale)).

It's called torrents. All the content on all the streaming platforms for an even cheaper price ($0).

The success of Medium has proven that lowering the barrier to write content is extremely valuable. If you're asking people to "work for free" then it should be as easy as possible and not feel like an errand. When you're inspired to write something, you just want to write it and not have the computer get in your way, or else you'll understandably give up. Wikipedia also proved this a couple decades ago.

Also rolling your own wiki is beyond stupid in this day and age. Just import all the MDN articles to MediaWiki. Making a script for this is a one-person weekend project. As I understand it though, Mozilla owns the copyright to all the content and they might shut you down for doing so.

I started using webpack in 2015. It's still the tool I reach for when doing JS. It's not going anywhere.

Apache, GNU, Boost

The kiss of death. It's a graveyard of things from a previous era, pure maintenance mode. I think library authors get tired of maintaining for free then hand it off to these life support organizations. The new way for open source software is a decentralized ecosystem where people fix software they actually use, so the cream rises to the top on its own and you don't need the sponsorship of these digital museums.

JSON is popular because of JS and web browsers. It's the native serialization format of the most popular platform, so naturally it is the most baby ducked. There are also pragmatic reasons such as browsers and various interpreters (Python) being faster at JSON than alternatives (thanks to years of hand optimization).

From an aesthetic point-of-view, XML is ideal. It reads like S-expressions or Lisp but with enough features to be a robust serialization format or even represent code. Validation alone puts it ahead of JSON. Too verbose? What kind of editor are you using that can't add the closing tag automatically or show you validation errors as you go. If type checking is good, then XML is good.

The main reason XML is hated now is that it's too difficult to learn.

People that care about performance will use protobufs/capnproto, which has all the safety of XML and more. People that want something to work out of the box everywhere without too much thought will use JSON. There is no room for caring about correctness for its own sake.

TOR, at the moment, is based on TCP and since the whole architecture is based on the assumption of TCP, I don't see it changing anytime soon. QUIC means TOR is now "legacy" unless we just do the right thing and boycott QUIC.

With a car you can go anywhere.

Who needs a train?

3000 bits for every inode. Academic excellence.

They should use ZFS or really fix btrfs. These barebones filesystems have really run their course.

Not hostile.

Just pointing out the hypocrisy of embracing "openness" and "free software" that anyone could use freely, then getting mad when someone does use it.

Also it's funny to see the FOSS crowd rediscover the need for intellectual property, having denounced it when it was applied in the opposite direction.

If you don't want someone to copy it, don't put it up on the internet.

> there are async await semantics

There are coroutines in C++20 now. It has the async/await syntax except it's extensible to any kind of coroutine semantics, not just Futures like in Rust.

> locking is way better

RAII was inspired by C++. For making a mutex own its associated data, that's a simple template class which is a well-known pattern. You're also not forced to use it when it is not a good fit.

> The syntax is cleaner

You got me, I have been trolled.

Someone should make a Rust Graveyard website like the "other" graveyard website except this one is for people giving up on projects due to an unaesthetic and pedantic programming language.

> Software written in any programming language (as long as it targets WASM) is a lot easier to host than existing models.

For the past 20 years you have been able to target x86 gnu/linux and have it running without modification on a readily available server, either your own hardware or rented/public cloud. How does switching from one binary format to another (x86 to WASM) change anything (except maybe slowing down your code)? As I understand it, the main draw of WASM is running non-JS code in a web browser.

It's not nuts to run servers. If an application is operating at any scale such that there is a nonstop stream of requests, then it will be cheaper, faster, and more energy-efficient to run a hot server. This follows from thermodynamics. No matter how good the cloud vendor's serverless is, it's always going to be less efficient than a server, unless it doesn't do any setup and teardown (i.e. no longer serverless).

It is nuts to run one server. Then you're wasting money with a server/VM. That's what serverless is ideal for: stuff no one uses. That's a real niche. Who's going to use that? Not profitable companies.

Often I think for most cases where you reach for serverless, you should reconsider the choice of a client-server architecture. An AWS Lambda isn't a server anymore; it's not "listening" to anything. Why can't the "client" do whatever the Lambda/RPC is doing?

Maybe what you want is just a convenient way to upload code and have it "just work" without thinking about system administration. The types of problems where you don't care about the OS is once again a niche. You probably don't even need new software for these kinds of things. You can just use SaaS products like Wordpress, Shopify, etc.

Serverless won't be profitable because the people who need it don't make money.