rpbiwer2

So then how do you run it unmutilated?

Yes, because the code you (or the LLM) writes is only part of the equation; if you use third party libraries then it becomes an ecosystem problem. I'm not currently using much Python but my understanding is that the community has not yet aligned on typing nearly as well as the TS community has.

> Considering that the recent Google code leak only substantiated that Chrome is the honey pot for surveillance and data harvesting that people long suspected

I'm vaguely aware of a code leak but haven't delved into the details; I'm curious if you have a link to details about this data harvesting?

The Internet existed before Internet ads (and particularly targeted ads) did. Personally, while I don't necessarily disagree with the point you're making, I'm curious to see what a pendulum swing in the opposite direction might look like.

Really? I've gotten the sense that the Rust community is more kind to noobs than average. Not that the average is great, but still.

I can't cite my sources, but I recently started learning Rust and I've been doing this. I would guess that I picked it up from the Rust book, since that's been my primary learning source.

I know I _could_ define my own error type, but that's tedious, especially if there are many types of errors to handle. For my (non-production) purposes it's been fine.

What's the idiomatic way to handle errors? Is there a way to collect more detailed error information without excessive boilerplate?

I feel like I often hear these kinds of stories about Uber, but rarely about Lyft. Is Lyft actually better, or are they just more under the radar?

"Quone" is another good Scrabble word, though it's usually only found in medical dictionaries.

I just want to thank you for your contribution to this thread. I've long thought email should go in a direction similar to what you're describing, and I appreciate the specificity you've provided.

I wish I could say I'm surprised by the animosity (and relative lack of substance) in some of the comments you've received, but I guess that's a problem with social media and/or humanity that's unlikely to have a technical solution.

This seems like the type of thing that a sophisticated query planner in 2024 would be able to figure out on its own? Maybe as a non database expert I'm expecting too much?

I'm out of touch. What would you use instead of ARM?

I was skeptical at first - tried the copilot beta, got annoyed by it, and quickly turned it off. Later I tried it again and haven't looked back.

For the most part it's not that I'm ceding the thinking to the machine; more often it suggests what I was going to type anyway, which if nothing else saves typing. It's especially helpful if I'm doing something repetitive.

Beyond that, it can save some cognitive load by auto completing a block of code that wouldn't have necessarily been very difficult, but that I would've had a stop to think about. E.g an API I'm not used to, or a nested loop or something.

The other big advantage that comes to mind is when I'm doing something I'm not familiar with, e.g. I recently started using Rust, and copilot has been a major help when I vaguely know what I _want_ to do but don't quite know how to get there on my own. I'm experienced enough to evaluate whether the suggested code does what I want. If there's anything in the output I don't understand, I can look it up.

> Are there tasks where you explicitly avoid them?

Not necessarily that I can think of, but after having copilot on for a little while it's gotten easier to tune it out when I'm not interested in its suggestions or when they're not helpful.

> How often do you find bugs in the generated code (and a corollary, how frequently has a bug slipped in that was only caught later)?

90% of the time I'm only accepting a single line of code at a time, so it's less a question of "is there a bug here" and more "does this do what I want or not?" Like, if I'm writing an email and gmail suggests an end to my sentence, I'm not worried about whether there's a bug in the sentence. If it's not what I want to say, I either don't take the suggestion, or I take the suggestion and modify it.

If I do accept larger chunks of suggested code, I review it thoroughly to the point where it's no longer "the AI's" code -- for all intents and purposes it's mine now. Like I said before, most of the time it's basically the code I was going to write anyway, I just got there faster.

I feel like in part it's an education issue. I don't have the slightest clue - was never taught - what is ok to eat and what is risky. I rely entirely on gut feelings and Google.

This (developers having significant time to work on hobby/side projects) seems to be pretty common among experiences I read about online (i.e. Hacker News, blogs) but basically unheard of among people I work with/talk to IRL. I'm very curious how people manage to carve out this time? Personally I find it very difficult. It was virtually impossible when I had a full time job - I guess that's what full time means. But now I work freelance, and while I'm able to spend some of my "work" time doing things I want to do vs need to do, I still have a lot of actual work to do and thus find it very hard to do anything meaningful with my "extra" time.

One major caveat is that PWAs don't have all the capabilities of a native app. I think that's the biggest issue people have with this -- if PWAs had full feature parity with native apps, I'd agree Apple's app store monopoly wouldn't be a big deal.

I think there are many reasons why something that people do want might not (yet) exist. For example, a monopolized market where customers don't have many choices. Or like you mentioned, difficulty in competing with incumbent advantage. Or maybe people just don't know what they want (e.g. "faster horses")

Android's app store may suck, but at least it's possible to start a competing store which sucks less.

Seeing as how this is Hacker News, I thought this was going to be about how the constitution contains non printable characters or something.

Maybe I'm dumb but that section didn't explain the problem to me in the slightest.

Is not being creepy sufficient? My understanding is that you need consent to collect literally any PII, e.g. an email address.

You've touched on some good points. It makes me wonder: what kind of objection can one raise that would actually make a difference? Send a mean tweet? Call my senator? And tell them to do what?

IMO simple objections will not sway tech platforms from the status quo of free-for-all data hoarding. We must vote with our feet and move away from the data-hoarding incumbents towards user-centric alternatives. Where suitable alternatives don't exist, we'll need to create them.

> I can get rid of all these lightning cables > Will have to buy more USB-C cables, though

Finally Apple's switched to USB-C so that we can cut down on cable waste!

I have no expectations, but I thought I might as well ask: do you know if there are any apps that will unroll a Twitter thread given a link like the one in your comment? The web version of Twitter no longer shows threads, and I've spent enough time scrolling through the shitty Twitter user page UI looking for old tweets that I'd really prefer an alternative if there is one.

I hear this all the time and I don't understand it. Bootstrapping a new project with <insert modern framework here> is so easy and fast, literally easier than bootstrapping a vanilla HTML project. What am I missing?

Edit: downvoters, I'm genuinely curious to hear your perspective.

All of the modern frameworks do tbh, people just like to bitch about what they don't understand

I agree. I don't have aphantasia but most of the time when I look at an architectural diagram it feels like I'm looking at nothing at all.

> use a domain that you can move to any provider and keep a backup of you're email.

And which ones are those? Once I've selected the right provider, how do I reliably implement my backups?

> If you put yourself in a place where someone can take everything from you than it's a real risk that they might.

I'll just go ahead and stop using every major software product created in the last decade.

Despite my sarcasm you're not wrong, I agree completely with what you're saying. But to follow your advice is not easy, especially for the average user. IMO it's a problem with the way software is made, and while many of us are vaguely aware of the problem, there's been little progress towards solving it.

Sure but my gripe is with those who already use TS

IMO the benefits of TS are huge, but probably the biggest benefit is that refactoring becomes almost trivial in most cases - just change the type of a variable/function/etc and the compiler will tell you every line in your codebase that needs to change in real time.

I agree, but I do wonder why the knee jerk reaction is "I'm not going to need it". The setup cost is basically zero! If TypeScript offers any benefit at all, why _not_ use it, since the benefits will come at near zero cost?

Agreed, "we will not sell your data" is a straight up lie if you eventually end up selling the data.