geekles

I agree with this statement.

Twitter as a platform and product works better today than it did a year ago. Less bots makes a huge difference.

It's also not hard to imagine why they lost 50% of their advertisers. 50% kind of lines up with the percentage of "woke" (horrible label, but whatever) companies out there who basically "had to" pull their ad dollars to not piss off the camp they put themselves in.

Prognostication is fun, but to be honest, we don't really have any idea whether or not this rebranding and redirection will work. Time will tell.

I, however, applaud people willing to take moonshots.

They should have been doing this, but California is currently mis-governed.

As if this will be limited to "iThings". If you don't think this tech is coming to all devices, you're not paying attention to the state of the world.

Mac support in games is less important now than ever before. Services such as Shadow are how I game on my Mac now.

The word "should" implies non-conclusivity.

You've never encountered badmouthing from a pro builder about other tool brands? How many did you talk to? Builders make the Ford v Chevy debates look minimal in comparison.

Sidecar adds a Touch Bar on the iPad to all Macs that support Sidecar.

The new Microsoft Edge has prefers-color-scheme as well.

Hyper2 is pretty good for windows. Also the built in VSCode terminal is serviceable.

No, actually, it doesn't.

What helps to prevent spammed low quality apps is the app review process.

Those who are spamming the app stores with low quality, keyword dense apps are those who are looking to make a quick buck, and they do not hesitate to pay the paltry yearly fee.

The point of a PWA is that the app store is not needed. Why would you be trying to get a PWA into the app store?

HN would disagree with the one rant the author spent the longest time on.

Perhaps the Wave protocol could be adapted to this sort of purpose. It seems designed for it, really.

I got started in grade school. We had a bunch of Apple IIc's and IIe's. We learned basic. I believe my first "real" program was a graphic of Spuds McKenzie, the Budweiser dog.

I didn't do much serious programming until I was about 24, the place I worked, a convenience store, just got cash registers with scanners. So we had all this scanning data but no easy way to collate it over time. I wrote a perl script that would parse our scanning data and tell me how much of x we sold for a period of time y. That was when I truly got bit by the programming bug.

My advice would be to have a problem you really need to solve, a goal. The rest is just trying to figure out how to make your language of choice reach that goal for you. It is so much easier to learn how to program when you have a real, tangible, and personal goal, and not some arbitrary exercise put forth by a language tutorial.

Something I wish I knew before getting into programming? Language choice is personal. Find a language whose syntax you enjoy and you can wrap your head around. Don't get caught up in language wars/debates. It's basically meaningless (although fun to argue about). Whatever language you enjoy the most is the one you should be using.