jmk1ng

...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

LGTM!

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.

Nothing wrong with Java or JVM based languages. They're just not the shiny new thing anymore.

I don't know what kind of software you write at your company. It could be that the JVM was a poor fit for the stuff you do and Rust is far more suited. Or it could just be someone in leadership read a blog post where some company migrated from Java to Rust and saw a billion percent perf increase despite their use case being specific and not at all applicable to what you do and decided to decree that everything gets ported to Rust.... or any dozen of reasons in-between

Plus it has a large library of great games that can be found cheap/used. Easily worth $100

Most of what you'd be playing on PS5 are PS4 games anyway

Of course. The well has been poisoned, and there's no way to know what any company's actually doing behind the scenes. I'm just lamenting that it had to come to this.

Buy the cheapest MacBook model you can find with an M-series chip and as much RAM as you can stomach the cost for.

I'd say 8gb is barrrrre minimum for doing app development. You'll want 16gb.

Listen, I'm the last person you'd expect to recommend a Mac. I am an Android guy. No other Apple products in my place.

...but I've owned every top end model from pretty much every relevant PC manufacturer just trying to find something as reliable, hassle free, and well built as my work Mac and it just doesn't exist.

The MacBooks are just in a whole other class. The battery life, the standby time, the speed of those M1/2 chips, runs cool and quiet.

I'm neutral on MacOS. It tends to stay out of my way. I don't use any of the Apple apps. It is usually stable as hell. My work MBP currently has an up time of 68 days without a reboot, and the only reason it rebooted last time was for security patches.

Build quality is unmatched, screen is great, trackpad is still a generation ahead of anything else, keyboard is great.

I accept my fate, Fediverse. Roast away

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.