HN user

TobyTheDog123

584 karma
Posts4
Comments303
View on HN

Exceptions are not the issue, Ruby's inherent "cleverness" is. Whatever problems the original commenter has with exceptions likely stems from this.

GitHub Spam 2 years ago

I don't think that's what the commenter is claiming. I think they want to be able to sue the companies who indirectly benefit from this kind of spam, which is pretty ridiculous.

However, crypto has become such a menace to society that it's time that governments do something about it, if they even can at this point.

Can we please stop pretending that Ruby/Rails is in any way a good choice for software that needs to be safe?

I do understand that it is what it is and GitLab has to deal with it, but going forward, can we stop pretending a language and framework that prioritizes cleverness and hidden control flow is better than something more boring?

If I sound overly-annoyed it's because I have to work on a production Ruby codebase where I can absolutely see a scenario in which we have similar issues just waiting to be exploited, because someone thought seventeen layers of abstraction made the code super extensible.

I just love how we can have a critical study about a failure that could have possibly led to the death of dozens if not 100+ people, a failure in something as routine and critical as flying in an airplane, and the article is behind a paywall.

We're getting very close to the point where the combination of the competency crisis and the greed crisis are going to start causing more people to think twice about doing things that were once common, like flying commercial.

Personally, I cancelled my flight later this month and am going to start getting in the habit of doing long road trips again.

Just-as-if-not-more dangerous? Maybe, but at least I have a higher chance of my fate being in my own hands (swerving out of the way of an oncoming truck vs being sucked out from a fuselage plug failing).

More inconvenient? Yep, don't care.

More expensive? Maybe, don't care.

It's funny that they're using peer-to-peer to literally mean sending payments from one person to another, rather than it being the technical definition.

I wonder if it's a marketing gimmick to make people think it's more libertarian/secure/private than it actually is.

Am I missing something critical here?

Why would people want to send payments over Twitter (I understand it's X, but I'm using Twitter to emphasize that the product is still, exclusively, a microblogging platform with some audio features).

Is it to donate to personalities? I can see that use-case, but whenever I see these kinds of headlines it seems the vision to create an "everything app" means that "peer-to-peer" payments means adding something like Venmo or Cashapp. Do people add their IRL friends on Twitter? If so, why would they use Twitter for that sort of thing as opposed to Venmo or Cashapp?

I'm genuinely curious, but to me it seems like it's a play to get hordes of cash flowing into the platform so that X can rake in interest on it for use in their own debt payments.

...the product teams that are left after pruning should try to keep the most experienced employees, lay off the junior ones...

I think I know the generation the author belongs to

The entire reason this is a big deal is that people don't know what their dependencies are. The left-pad incident wasn't a big deal because it was pulled, it was a big deal because no one could easily fix their builds and didn't even know they were depending on it, because it was a dependency of a dependency of a dependency.

While it's ridiculous to expect that people will audit every single dependency and sub-dependency, it's not ridiculous to expect tooling to do the same.

Packages should be given an overall quality rating (and honestly it might be great for an ecosystem as large, diverse, and welcoming-to-beginners as JS/TS), part of the score comes from the number of different dependencies/sub-dependencies -- a social package score if you will. If a package causes the dependency graph to explode, give a warning before installing it.

Then, if you're NPM, you don't need all of these convoluted and exploitable policies around un-publishing.

I think those are two different scales.

Libertarianism <---> Authoritarianism

Capitalism <---> Communism

Usually the sweet spot is somewhere in the middle of both, which is what the United States is (though some may argue we've begun to slide towards the extremes)

The burden should be on them to ensure their child is not consuming porn

This argument is essentially that it's acceptable for websites to show porn to children if their parents don't care or are fine with it.

It's a horrible, dangerous thing regardless of if parents are involved are not, and therefore should not solely be the responsibility of the parents.

(Unrelated to the OP - but I've been so frustrated by this for so long that it's worth the [flagged])

A product like this is exactly what I've been looking for with pretty great pricing.

The one thing that this (and most providers) are missing is making email easy to test. I'm about to launch a product where email is critical, and there's no way to send an example email (with a non-test email address) to your service and see that you receive it, without it being sent to the To address.

Better yet, the few providers that do support it charge as if it were a real email, when none of the delivery costs exist on their end (there are infrastructure costs, sure, but there is none of the reputation risk nor need for clean IPs, the reason people use transactional services like these in the first place).

With Twitter being worse than ever while also implementing the paid-for blue check, I'm no longer convinced that nominal costs solve much of anything. Maybe it's a different model (per email vs per account w/ Twitter), but I feel like scammers/phishers would pay the premium.

While extremely idealist and would never happen in practice, I think I'd rather see a provider that enforces KYC-esque requirements and is a closed iMessage-esque system. I took my phone number off my main mobile device due to spam (pretty much everyone I know has an iPhone) and have not looked back since.

If I want privacy, I'll self-host. If I don't care, I'll use the monopoly.

It's strange that I have the opposite feeling while consulting.

I work for a "big tech" company and do consulting work on the side, and it's the former that has all of the Slack/Zoom/Agile/meaningless nonsense -- with consulting I feel as though I'm actually solving a problem for a business in a meaningful way.

I guess all consulting gigs aren't created equal - I guess I've managed to avoid the bad ones so far.

You're right - I should have clarified that I'm talking about new projects - as in "Why would someone choose Postgres over one of these distributed SQLite providers for a new project?"

(I'm sure those use-cases exist, but I'm not sure if they exist inside the use-cases Supabase supports)

These two companies have pricing models that I just absolutely hate.

On one end of the spectrum you have Supabase - a very Vercel-esque "developer platform" with tiered offerings that ensure that you're paying more than you're using.

On the other end of the spectrum you have Fly - a very Lambda-esque offering with hyper-specific per-second per-memory per-cpu pricing where you'll probably end up paying too little and getting performance hits.

I really do not understand why people would do either when things like Cloudflare Workers (et al) exist. Why do people still want to worry about scaling?

I'm glad there's a spiritual successor to Apollo, but it's not entirely about comparing one cost to one cost.

-

Spotify: $10.99/mo ($132/yr)

YouTube: $13.99/mo ($168/yr)

Twitch: $11.99/mo ($144/yr)

Narwhal: $6/mo ($72/yr)

-

You'd be right, the $72/yr for Narwhal is less than the $100/yr developer certificate, but with all of the other sideloading opportunities it's no contest w.r.t cost.

Apollo is one of the few reasons I shell out the $100/year for an Apple Developer Account.

If someone is even mildly technical I'd recommend going the Sideloadly route for getting Apollo, ad-free/background-play YouTube, ad-free/backgroun-play Twitch, and ad-free Spotify.

While this is incredible and I can't wait to use this with HTMX, I really wish it didn't require a CLI to generate the *_templ.go files.

Code generation is something I saw in Flutter/Dart a lot and it entirely killed my interest in it (mostly with JSON serialization/deserialization to classes).

Thankfully, it's by no means a show-stopper for me thanks to their hot reloading functionality. https://templ.guide/commands-and-tools/hot-reload

Waveterm 3 years ago

I thought it was just the marketing trying to show off too many features at once, and I'd really like a more workspace-centric approach to terminals, so I gave it a download -- unfortunately the actual UI is worse than the screenshots they show.

- Sidebar that is either HUGE (and branded) or nonexistent (I'd like to see something like Discord's approach here)

- Only UI settings are a font size selector

- The input and cwd are on different lines for some reason (though it shows huge helper text inline with the input)

- Weird borders and shadows on elements that are super jarring.

EDIT: Nevermind, I somehow totally missed the "beta" plastered all over the place.

I just gave Orion a try because of this HackerNews post --- what a buggy mess.

I've already seen three crashes using it, mostly by bookmarking things or deleting old bookmarks.

I'm very grateful that there are good players entering the space (from what I hear Kagi is amazing), but Orion just is not ready to be a daily driver.