wgoodall01

This has been seen in a mainstream lisp before! (sort of)

Wolfram Language uses almost this exact syntax—function application looks like f[x,y], but in all other respects, it works like a LISP would.

Replace "text editor" with "IDE," and that 700mb figure doesn't seem so extravagant.

I feel that this isn't quite a fair comparison.

Take any other language with a web framework---Ruby with Rails, Java with Play/Spring, any web server which exposes a CGI interface, Python with Django/flask/whatever---and you will find a colossal amount of framework code behind the simple "hello, world!" demo.

Web apps are complex things, especially when the framework has to account for common cross-cutting concerns and patterns elegantly and succinctly. The fact that the JS ecosystem with NPM exposes that complexity to the user directly with an (albeit massive) node_modules installation isn't a strike against node per se: other languages have this code too, they just don't stash it all in the same folder as your project.

If you want to criticize the JS ecosystem, doing it on the basis of sheer SLOC downloaded by an `npm install` isn't too great.

We can talk about the quality of these packages, or about code review standards, or about the unique challenges auditing code from many sources for bugs and security problems. But talking about how the framework code gets installed seems counterproductive.

I wouldn't agree with that---media players are often fed untrusted content from the Internet, so a security issue in a shared media player API can be critical. See the Android StageFright vulnerability from a few years back.

Writing it in C for a marginal performance gain just isn't worth it.

Isn't it better to crash than to fail silently, possibly storing malformed data?

I'm a student, mainly using GCP for hobby/hackathon projects, and to teach myself.

I am massively excited about Cloud Run's free tier---for someone with a budget of zero, being able to get a project off the ground and functional without paying through the nose if you forget to turn down some service is incredibly useful. Getting an unexpected $40 App Engine bill at the end of the month isn't fun.

I'm definitely going to check Cloud Run out as a go-to for future projects--it looks like a really good fit for my use case.

Basically, that sounds like a union for app developers. That might end up being a positive thing.

I mean really, what's the difference? They can access that file at any time they want anyhow---as long as they only send it to their server after user consent, I'm really failing to see a problem here. Making a copy of one file they can already access to another place they can also already access isn't really violating anyone's privacy. It's what they DO with the information that matters.

I'd say that the massive investment is necessary because of how uncomplicated this particular system is. Without a large, sprawling, and well-funded project backing it, a simple (and probably far more reliable) solution can lack credibility when compared to more complicated alternatives.

Iirc, you can buy Lightroom 6 perpetually, no creative cloud needed. Might be worth looking into.

You might want to do that soon-ish, just because of the flakiness of most hard drives. Take a solid backup of the files and put it somewhere reliable.

Although it's hard to look through personal files like that, it's even worse if you had the opportunity to, didn't do it, and the hard drive failed.

Although raising kids without access to TV/social media may seem like a great way to avoid their downsides, like ad targeting, it ultimately only serves to cut them off from their peers.

TV and social media serve as vital cultural references that kids have a social need to be 'in on.' It is one of the most awkward things when you're the only one in a room who has no clue what everyone else is talking about because you didn't see that post, or watch that show.

So while social networks may be bad, it's just as bad to cut kids off from the culture their peers are regularly immersed in.

Create-react-app is the way to go for beginners. It gets you up and running with the full toolchain with 0 setup or configuration - you can get right into learning React itself. All you need is node, npm, and an editor, and you are pretty much ready to go.