Jobs looked bored.
I'm bored.
This guy wasn't a God.
This is just a rudimentary PR-enforced interview capture.
The way people hang on every mundane word that comes out of certain people's mouths is tribalistic to a disturbing monkey degree.
Do you have any idea how much bloat Spotify has that it can cut? Have you ever seen the NYC office? It's padded with hundreds of overpaid "creatives" poached from every NY agency who do nothing more than create unnecessary traditional marketing campaigns, all of which serve no one, while spending 80% of the day snacking on premium goods and watching insider music acts in their gigantic, swanky, luxury office space.
Source: Been there, seen it, a long time. Spotify needs to be nothing more than a functioning music utility. Instead their US offices are structured like a massive, bloated, 90's style agency party zone.
CSS animations are a pain-inducing non-starter for thousands of recurring use cases.
Example: Using Javascript to SHOW a modal, but then relying applying addClass('animate') using CSS animations to transition that modal (eg: bottom of screen to center, while fading in) are nearly impossible without tons of hackery. The animations do not render.
It's sad reading comments like this from bandwagoners who haven't read a single academic or technical whitepaper on the technology, let alone the hundreds of them that have emerged which prove / annotate / express / clarify, in exhausting detail, all of the "fundamental problems" that Bitcoin's PoW protocol have, as well as far superior approaches that are in the process of being implemented.
But it's cute. You like Bitcoin. You're a good cheerleader.
I've actually read every single paper on Bitcoin, on Proof of Work, and on Proof of Stake I've ever found. I've been involved in Bitcoin since mid 2010. What is sad is that you wrote what you just did as if that dismisses me, or as if you are in any way authoritative on the subject. Your snide passive-aggressive writing is not cute. I am not a Bitcoin cheerleader, and I'd just prefer not talk to anyone about Bitcoin. It's been years since I have done so, I no longer go to conferences or even talk to family members about Bitcoin, and it's much the same way I quit telling people about linux maybe a decade ago. HFSP.
It's weird how hard you go against literally anything except Bitcoin because of your rabid obsession with whatever paltry sum of money you've made over this one dated technologically is. You're literally like a cancer-ridden coal miner coughing his last lung to keep the mines open. Good riddance.
I missed this at the time, but this sort of personal attack is absolutely not ok on HN and will get you banned for obvious reasons. You've unfortunately been breaking the site guidelines in a bunch of your other comments too.
Can I ask what value Cinder has in a world of Unreal/Unity? I'm guessing you don't use Houdini either since it's not realtime.
But take Unreal for example: you have this absolutely massive world of presets/plugins/etc made by the community. You have Niagara particle systems. You have incredible post-processing / color correction / cinematic grading / etc. You have Blueprints, the ability to write code, etc. You have the entirety of Quixel's megascans, etc. It's almost completely effortless to make unbelievably gorgeous/immersive things, whether it's near-photorealistic environments/landscapes, abstract audio visualizations, full on games, etc.
I'm genuinely trying to understand why anyone who works in interactive/realtime 2D or 3D visualization would ever use Cinder or Processing these days. Thoughts?
Coming from a game networking side, why wouldn't you want to embrace a WebSockets world for everything? The upsides seem so incredibly intuitive for someone looking at it from the outside of traditional web development.
Traditional SQL databases aren't very streaming-friendly, so you more or less end up building an entire secondary push system just to figure out when to send what updates to who.
Mostly just the intuitiveness of the architecture. I don't need bi-directional if I'm mostly just showing you some forms in a CRUD app, and client-initiated request/response is simpler to reason about.
Bi-directional gives you more power, but you also have to think harder about the protocol and application state once the server is also pushing events to the client unprompted.
Scaling not just technically either, it's also the engineers. Most Web engineers have had their minds bent to the request response model with databases.
The key reason is that a game lasts... minutes to hours (ignoring most MMOs), so the state machine makes sense and the risk of failure low. Web devs have to use a database which has state for years.
Plus most games are awful at handling connection issues, you'll be dropped from the game and have to reload the entire map and assets again, often taking 30 seconds or more to rejoin.
I'm not sure we should be taking advice about how to load information on mobile devices with spotty connections from the gaming industry.
