Hacker Newsnew | past | comments | ask | show | jobs | submit | mervz's commentslogin

wtf are we doing, man?

100%.

It's similar to AI... the only people trying to tell you "it's the future" are those with financial stakes.


There have been people going back to Turing thinking AI is the future and I don't think he was trying to pump his AI stocks.

Yeah. Rosenblatt, von Neumann, McCarthy, Weizenbaum... buncha morons

I feel very different about AI. I have still no clear idea what crypto is good for except money laundering. AI feels very different. It might not live up to all it’s promises. But it is clearly very capable.

The difference is that AI is a huge array of technologies (not only LLMs) and are being used in several fields with different, useful purposes.

There's a cult and a bubble too, though, and I agree with that part.


You're forgetting the true believers.

Crazy that people really need instructions on how to self-host stuff these days... this stuff used to be something most devs could figure out.

I noticed this in development mode but performance improved substantially in production


You seem to be an extreme outlier and probably not the target audience for such applications. No offense, but nobody is carrying around multiple devices when the one device we all have can do everything and do it better.


It's a dead end for your use case, let's be very clear about that.

And it's funny that you think anything about React and/or Vue is 'trivial'.


Surely you’re not saying the frameworks famous for ui = f(state) actually suck at managing state…


If it only were true. React is nothing like ui = f(state). More like ui = f(some_trivial_state) + lifecycles magic + probably global_state.

Garbage. But effective devrel.


This type of dismissive attitude is so strange to me. The only reason "lifecycles magic + probably global_state" would be causing your app to behave unpredictably is - this is going to shock you - because you closed your mind to a tool by dismissing it as garbage before you used it, and then failed to use it properly because you think its popularity boils down to PR.

For instance, you could entirely forgo the influence of lifecycles and global state by putting everything in a top-level Context with 1 state object that you only ever update by calling `setState`.

After that, you might find reasons to optimize your app, which could lead you to more interesting approaches like reducers or state management libraries or memoization, but I'm guessing you would never get that far and just go back to what you were doing before, since YOUR preferences are battle hardened and reliable software, while things you don't know about are only popular because of Facebook. Obviously.


So, redux? It's either redux or, sorry, "lifecycles magic + probably global_state". And who uses redux in 2025?


Honestly, if you’re getting thru life with this attitude, good for you, but you might want to consider if it’s the only way


I'm doing fine, thank you. Perhaps you didn't understand what I said.

My best ballpark guess for global redux usage in react projects is between 25% and at best 50% if you include redux/TEA-like libraries, but not non-pure usage.

So yes, saying that react is `ui = f(state)` does everyone a disservice. It might be true for you, but it's probably not even the average.


Well, for anyone using Vue you get automatic observability baked in, right? And reactive programming state management libraries within react are plenty popular, not to mention the built in state management being quite literally UI = f(state).

The fact people use the tortured disaster that is redux isn’t really a knock on react in any sane person’s view, we all know the JS community is full of beginners who don’t know better


kinda does, tbh.


Everything you listed IS centralized, though.


I find Go's type system to be extremely lackluster.


Ok can you elaborate?


This is a diabolical take


Hate it all you want, but it's the sole reason Counter-Strike still exists today. Without skins, Valve would have shut the door on the game (and quite possibly the company entirely).

Skins is literally a money printing machine.


That's, excuse my French, fucking ridiculous. Steam is a money printing machine that affords Valve the capital to run its CS servers 100 over.

Skins are also a money machine but it's just false to claim without it Valve would close its doors.


You don't think they make more money with Steam?


Yeah... selling games other than CS. The reason CS is still under active development is because the market economy rakes in huge amounts of money. Some analysts have added up figure for the numbers of case keys sold, and those alone sell $1 billion / year. Plus they take cut of all of the other market transactions.


You can sell and make skins without the literal loot boxes


> sole reason Counter-Strike still exists today

Every other live service manages with non-gambling skins. They have their own problems (usually around FOMO), but nowhere near the literal gambling that is CS.

> Valve would have shut the door on the game

In terms of not having any developers on it, sure, not impossible.

> (and quite possibly the company entirely)

Ahahahaha come on man, even without CS, Valve is one of the most profitable companies of all time.


> Every other live service manages with non-gambling skins.

Most games that are that old, don't survive.


Arms Deal came out in 2013 [0]. 1.6 came out in 2000, so that is 13 years (not considering CSS came out in 2004, and CS:GO was in 2012, without any monetization).

Fortnite is coming onto 8 years old now. The idea of it being around for 5 years longer is not particularly alien.

[0]: https://blog.counter-strike.net/2013/08/7425/

e: Actually, I should really be focusing on the time from Arms Deal to the present, which is 12 years. So, Fortnite has even less time to catch up to CS' current lifespan with gambling.


Valve has already pretty much "shut the door" on its games relatively to how much money they have and how much dev effort they could put into it if they actually tried harder, because they're mostly just maintaining their gambling facades (cs/dota2/tf2) and abandoning everything else (l4d2/other stagnant games and ip).


#StopKillingGames

Did you miss the entire article? CS itself came from a dorm room. You can have excellent games that spawn from creativity instead of monetization.

I was really into the odd maps (NIPPER) and early Internet community around games (joe2). We hosted servers off of unused CPU cycles from oil exploration boxes.

This still exists all over the web, but the creators that figured out economics moved on.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: