I’m really good at searching Google. I’m a “prompt engineer” too

Did it work? How do you know that? A consumer of your package sends a int when your package expects a string.

What now?

Use whatever is most enjoyable to you. You’ll be most productive working in a framework you like as opposed to one people online convinced you was “right”.

Take an hour or two with each. Use whatever is clicking best with you.

All these options are perfectly sound.

This is the stupidest use of this stupid meme with this stupid piece of shit that I’ve ever seen

Blockchain? Oh, hah, no no… none of us were ever hyping up a tech we didn’t understand as the solution to literally any problem.

Say, have you heard about AI? It’s a revolutionary technology that’s the solution to any problem!

Which is fair. If it’s something you use all the time, obviously an app is usually going to be the way to go.

But the reason they want you to install the app is so they can send push notifications and track you more effectively

https://youtu.be/CtUuab1Aqg0

A classic

On the off chance you’re actually serious.

The thing I was pointing out is that you have a union. Unions are actively and aggressively busted by US companies. Almost every US state has “at-will” employment laws that mean you can be laid off at any time for pretty much any reason at the drop of a hat.

All of a sudden that 400K or whatever you were expecting to make this year turned into $0. You no longer have health insurance. Those RSUs you had vesting this year are gone (and those RSUs made up a big chunk of your compensation - that’s how people get into the 300-400K+ a year numbers).

The highs can be high, but the lows are very low.

…according to my union statistics…

I mean… you’ve got to be trolling at this point. No one is this clueless.

BUILD SOMETHING.

Learning concepts without the ability to apply them are essentially useless.

Get your hands dirty and build something that would be valuable to you and solve a problem for yourself.

Don’t get hung up on doing it “right”. Focus on making it work. Don’t worry about how it’ll work for a million users. Right now your focus is on making it work for one user.

As you go you’ll hit walls. Research how to get past them and keep going. Again, you’re going to make mistakes. DO NOT GET HUNG UP ON THIS.

Making mistakes is part of the journey. Even the best software engineers in the world rarely get things right their first try. It’s part of the process.

I feel like we’re splitting hairs here. MIT is an extremely permissible license. The fact someone could take this and make a closed source fork doesn’t affect the existence or openness of the MIT licensed releases

https://github.com/bluesky-social

Even their web and mobile clients are FOSS

The FUD and misinformation on here about Bluesky an AT is wild

Bluesky is still in beta. It’s intentionally not open to the general public because federation hasn’t yet been opened up and they only have one instance running.

The nice thing about Bluesky’s architecture (over ActivityPub) is the fact your content and identity is portable. So you can move over to a different instance as they start to come online.

I think the important takeaway from articles like this is the fundamental misunderstanding of decentralized social protocols. It shouldn’t be on one central authority how things are moderated globally. These kinds of articles kind of prove the point.

I was a big fan of Vue 2. Vue 3 is a completely different library if you choose to adopt the composition API (which is where everything is headed). If everyone is going to have to learn a totally new composition pattern, might as well look at what else is out there.

Kinda similar to the big overhaul between Angular 1 and 2

Vue 3’s Composition API and composables are more similar to React functional components and hooks than it is to Vue 2 and its Options API. That’s not to say that React Hooks and Vue Composables are apples-to-apples. They still have different approaches to reactivity and so on, but the programming model is more familiar between the two.

Coming to Vue 3 from 2 was a bit of whiplash. However I’ve been working with it for a few days now and have come to appreciate how much more flexible and powerful it is to have access to Vue’s reactive primitives anywhere - you don’t have to write all your business logic in the scope of a Vue instance.

That said, it comes with a much higher learning curve. Vue 2 gave you guardrails, an easily understood component class structure, etc. That’s what I liked about it as it scaled well to large teams. Whereas React scaled to a large team quickly turns into a complete mess. Ask 10 different React engineers and you’ll get 10 surprisingly different approaches to how to implement components and architect applications.