Because React is JS and Svelte isn't
React is JSX*
Nothing preventing them from making an <If condition={…}>…<Else>… component
Readit NewsDeleted Comment
react didn't invent that syntax. This is a standard piece of C like syntax that most (but not all) languages with curly braces share. JSX/TSX used in react don't make this choice for you, you can use any javascript syntax which can be used when passing a value (eg in a function invocation, or variable declaration). If you don't like it, you are perfectly free to declare a variable and set its value using a regular if / else block and use it directly from the template.
My point is this is not a syntax decision that React made, but svelte's syntax was (as far as I can tell) a decision.
I mean, yeah, the ternary operator is part of JS syntax. But it WAS React’s choice to not include any alternative way to if/else add an element (there is an if/else but only for the entire component, not just for conditionally adding one element within a component). So indirectly this is React’s syntax decision.
Give a quick glance to Svelte.
Help me understand, how this syntax
{#if expression}...{:else if expression}...{/if}
can be seriously invented in our... more civilized age?
It’s not the most pretty syntax, but it’s wayyy better than React’s terrible (expression ? … : …) or (expression && …)
Nice work! The most surprising part for me was that your websites says you are 20 years old – so I gotta ask, what was the motivation?
I'm 39, born in 1983, so I have serious nostalgia around Windows 95. I was 12 when it came out, my parents bought a Dell when it was new and those years were very formative for me. I assumed that nostalgia would be the only driver to do this... But you weren't born until ~8 years after it was released. I'm genuinely curious (and impressed!)
Not the person you’re asking, but I’m 22 and personally I just love the pixelated OS aesthetic
I love pixel art, and Windows 95 looks so cute!
Deleted Comment
> please don't say just hello in chat
In a great many chat (as in one-to-many group chat as in, say, IRC -- where the 'C' stands for "chat" btw) it's perfectly okay when people join and start with just "hello".
I think TFA meant to write: "please don't say just hello in PMs to coworkers".
Not all chats revolves around leveraging synergies to maximize shareholders value while at work.
Yeah, also this:
> Imagine calling someone on the phone, going hello! then putting them on hold.
I literally start every call with “hello” and then I pause to see if they're there…
Godots signals are such a huge step up over Unity's built in classes having a lack of modularity.
How do you even make sense of that? Godot vs Unity basically have the same scene/node/component model except Godot does it better imo. Eg) What is the difference between a prefab vs a scene in Unity anyways? Basically nothing, it's just (I'm speculating) a tech debt mistake in their design, probably still going because of how light maps work today.
Unity's advantage over Godot is it's 3D renderer, built in physX, il2cpp backend for C#, profiler, general runtime performance and console support.
Godots design is objectively more cohesive, as Unity has simply splintered into 10 different design directions since ~2018.
I'm not trying to be a hater, I just think signals are a huge advantage for writing modular, simple stuff in Godot. I think there's plenty of great reasons to prefer Unity to Godot but "signals" is not one of em.
It is just so confusing to me and took me over a day to get a simple menu aligned how I wanted
it might just be me not understanding how it works though