toomanydoubts

That doesn't change much, I guess. Still very little power usage compared to an actual turned on machine.

If we start with the reasonable assumption that "being malicious" !== "hacking a bank account", then the answer to your question does not matter at all.

There are some "demos" on the homepage, although I don't think they do a very good job of demonstrating the app.

Klack is an interesting concept, but a really wish there was like a 15 minute real demo or something to really get a feel for what's like. I'm also reluctant of paying for it just to try it out.

Doesn't run with proton for me.

For those who are interested, there's also lots of classes about FP from Bartosz Milewski for free on YT.

How is that not true for JS given node?

The goal is to build better AI to make more money.

And a lifetime(thus not really an early retirement).

>So changing a column name or type, for example, is pretty easy to refactor, which may not be true for SQL queries and may take significant testing.

You can also get that with raw sql on the right ecosystem. I once developed a simple application using hasql and hasql-th(on Haskell). Very close to raw sql strings but with type checking at compile time. Feels like you're driving a lambo.

Or even worst: when you cannot switch out of it but you're not smart to package proprietary software that's not available in the repositories.

Much like online casinos that lets you quickly register and deposit, but will ask for ID verification when cashing out.

Yeah, clicked thinking about the same thing.

Yes. As a rule of thumb, unless you're making some kind of experiment/poc/artistic work please don't hijack the native browser scroll ever. Hate that this still has to be said in 2023. We like and (maybe) configured the scroll on the OS to our own taste, it's pointless to try and impose an slower, inferior and bug-ridden non-native implementation of the scroll just to add some kind of "smoothness".

I think Writing Editor sounds about right.

>Which is to not have a tool chain.

In my opinion that boat sailed the moment he implemented `download-package`.

>speaks to their commitment to strict security measures and good engineering culture

Does it really or does it just mean that nobody cared enough to do it for whatever reason?

In what ways are applets/flash superior to browser engines/JS? I really can't see it at all.

I love programming and I love software engineering. What I don't like is having to work for a living(in this case, doing SWE).

I never thought I would live to see this day! Thank you so much for the work

That was a fun read.

Doesn't most people who commit white-collar crimes do so because the riches acquired does matter in reducing time and getting out of jail quickly?

This is absolute madness. Just accept the game for what it is. If they wanna call software developers "software engineers", what do you have to gain by swimming uphill?

Aren't TikTok and Instagram and social networks?

I think the question that's not answered clearly is: why can Sass parse it, but browsers can't?

It says: "If they see a sequence like element:pseudo, they’ll parse the entire style rule as if it were a property: value declaration.", but why can't the parser be modified to work like Sass parser?

Maybe it's obvious for someone who has deep parser knowledge, but for someone who only has a superficial knowledge, this is not clear. If Sass can transform .sass into .css, what's stopping Chrome from embedding the full sass software and preprocessing all css files with it, *if really wanted too*? While not ideal for obvious reasons, what I mean is: it seems to definitely be possible to do. Does this all just boil down to "we don't want to have the work of rewritting the CSS parser"?

The other day I copied a question from leetcode and asked GPT to solve it. The solution had the correct structure to be interpreted by leetcode(Solution class, with the correct method name and signature, and with the same implementation of a linked list that leetcode would use). It made me feel like GPT was not implementing the solution for anything. Just copying and pasting some code it has read on the internet.

Too much effort for the reader to work out which one he's in, I guess?

That would've been cheaper than buying twitter for sure.

New challenge unlocked: design your application in an wrapper agnostic way to avoid getting locked out when the wrapper service bans you.

I understand that it looks like that, but I believe most of the FP evangelists are just too excited about the cool tech and want to share it with everybody so everybody else can feel the joys of functional programming. At least that's why I often mention and talk about FP to other devs.

I don't see how that's an issue. Using photoshop doesn't automatically allow you to post the images. You can post the images IF it was not made/edited by an AI model, regardless of if photoshop was used.

If you use the Stable Diffusion plugin, then you're using stable diffusion, and therefore can't post the image. It doesn't matter at all that you used the photoshop plugin.