Cool idea! AFAIK emails are just sent as text but the client renders them when you read them. Theoretically it wouldn’t be hard to send markdown and add a header that indicates the body is markdown. Hard part is integrating support into the client. Since HTML is more verbose than markdown, and you can often mix markdown and HTML, this could actually lead to space and data savings!

I’d say it’s the tooling that sucks more than anything. I’ve had installations fail because of bad caches (and resolved it by doing things NPM advised me not to do), installations that take forever and seem stuck on one dependency, conflicts with ES and Common modules, node_modules folders that dwarf other folders in size, nobody makes proper use of devDependencies, some odd dependencies on Java or Python, and so on. I think the ease of learning JS has done it a disservice as you get millions of devs contributing but not all are trained as devs or computer scientists and you get a flood of libraries that all do the same thing and often even reproduce built-in functionality.

I really do enjoy coding in it more than any other language but when it comes time to run or build is when my rage kicks in.

Wait… what were we talking about? Oh, yeah.

Shitty web apps aren’t really the fault of the underlying tech. This is a problem of design and I don’t think the programming language really has much of an effect on the usability.

As far as improving your corner of the code goes I would say a consistent style is important but having 500 lines per function is not a style. If someone will complain about efficiency (function call stack etc) then someone needs to identify what parts are truly time-sensitive. It’s likely not the entire codebase.

Wrangling a monster code base really requires a product owner. If one person doesn’t own the application as a whole then there’s no hope of consistency in the first place.

Or at the very least, so long as its http driven, put a proxy in front and on the backend break up common features into microservices. With a proxy the consumers will have pretty much no idea they went from talking to one service to a dozen.

It’s been the hardest thing for me to instill good testing practices in devs. In a function with 23 paths devs usually burnout and only do 9 or 10. Most never consider that making the function smaller is an option.

True, but it still surprises me that a lot of universities have enrollment caps. If you want to be present for a live lecture, in-person or telecast, then you should pay a premium. Otherwise you should be able to take online courses in the style of Udemy and sit in for proctored exams.

Tutti Frutti. I mean, I hated it then and probably wouldn’t like it as an adult but it seemed to be everywhere when I was a kid.

Best case, rest of the world goes Star Trek while the US goes Mad Max. I mean, if everything got better worldwide I kind of feel like we’ll backslide again because people have no idea what struggle and suffering is anymore. The US can be a shining beacon on the hill proudly declaring, “Stay away! Dead inside!”

Depends. You could argue that economically speaking it’s not worthwhile to stop and cite people for speeding. Police do have discretion on that kind of thing so not the best example, but still, there’s probably stuff that isn’t good for the bottom line that just needs to happen. The government is not a business.

Now when I say “depends”, I would be more inclined to go after a small number of people committing massive fraud than a large number committing minor acts of fraud. In the first case I think charges would discourage future abuse but in the second probably not. It wouldn’t be a vast, organized network of people doing the same thing, but a bunch of people that happened to notice the same opportunity. I think you’d do just as well having applicants read and sign a paper that goes over the penalties of abuse (while spending very little resources on enforcement).

So one portal in an active volcano and…

The struggle with KeePass conflicts is real. Put basically the problem occurs when you change a DB on device A, change the same DB on device B, and then you sync them using Syncthing. That might happen for me once a month.

I think I found a process that can reduce the occurrence of conflicts, mostly, not entirely. Instead of one DB that every device shares I have one DB per device (i.e. the KeePass file includes the name of the device). Most of the time this can’t possibly cause a conflict because device A only saves to its own DB. The only time it could create a conflict is if I need to pull in an entry that I made on another device. That’s a manual process for me and it makes me more aware that a conflict could happen. I make sure the device I’m syncing from is active in Syncthing, and if it is there’s almost no chance of a conflict.

A one-way sync option for KeePass would make conflicts almost impossible so I think I’ll propose that or work on a plugin for it.

Hoping it remains viable for a long time without updates. Syncing my KeePass database is really key for me. I need to fluidly add and read passwords from at least 3 devices.