NFTs are not baseball cards, they're not JPEGs, they're none of this.
They are emblems of buy-in to a community or idea. Think of it like the next generation of crowdfunding.
Most of what people are saying here is really ignorant of the reality on the ground to be honest, so it's hard to say anything other than-- ya'll really don't see it, because you haven't bothered to look.
I went to a "blue ribbon" school that was attached to a continuation school. It was a great school. Kids behaved well, very upper middle class.
However, if you were doing at all not great for any reason -- C average, struggling with depression or learning, anything -- they would pressure you into the continuation school right next door. So you have one school operating as two schools so that they can pretend to be the top school in the state by moving the bottom set next door.
People, when picking a career in college, still seem to believe that you can have a 9-5 job for life. I know quite a few university bank employees (ubs, Barclay's, etc) before and/or now still in London who are not programmers; sure they make more, faster after uni, but they work stupid hours. And get kicked fast if they kick up a fuss.
The expectation that things are like what you were told by parents or grandparents maybe needs adjusting. You are not hireable with this attitude, it is not a programmer-only problem.
I tend to agree, but there's been two competing posts on HN today, one about attracting developers like ants to honey with exciting new technology and the other about avoiding hype and delivering products with stable tech.
If i were a lawyer, I'd go to school once, and reap benefit form that education as an assets and build on it with experience.
Software is not like that. Yes school is an asset, but it dates, and so does experience when the market moves constantly.
The problem is that there are a lot of technologies that are simply insufficient or bad. jquery is critically insufficient. A lot of one way databinding frameworks are merely insufficient. The reason why react and the VDOM won is that it's literally just client side html rendering with the exact same flow as a server side html template. VDOM is merely an implementation detail that makes this type of client side rendering efficient enough that you can trigger it all the time, no matter how trivial the interaction is.
Although I personally dislike React itself and rather use preact I consider the API itself to be pretty solid and definitively worthy of building a career on top of it that would last at least 10 years. Above a certain level of sufficiency any change in framework/language is just churn.
I consider PHP to be critically insufficient because you have to force people to learn Lavarel otherwise they get the stupid idea of writing an old school apache PHP app. It also has some stupid warts that provide no value. Overall it's not meeting the level of quality necessary to build a career on top of it. The only benefit it provides is that once you learn all the warts its merely ok.
Java is also insufficient because it is missing very simple features. The foundation is solid but the details just aren't there. Getters and Setters shouldn't be a thing. They only exist to please certain frameworks and some theoretical futureproofing. Replace them with properties (that automatically generate getters and setters) and end the discussion right there. It's really sad how much effort it is to write a small data class in Java. I have a small project where I chose to use groovy simply because I had to define 30 data classes. With Java 50% of the codebase would be getters and setters to please the serialization library. Groovy is mature but it's not exactly popular, since people who don't want to use it are forced to use it (Gradle).
The software industry isn't mature. That's the reality. There are lots of established but insufficient solutions. There are lots of sufficient but not established solutions. React is right in the sweet spot. PHP is clearly insufficient. Java is insufficient but close. Modern languages and frameworks rarely get traction and are replaced all the time. Groovy is something that you could in theory build a whole career on but the jobs aren't there.
Await with promises vs monadic promises is also a point of contention. The only thing that everyone agrees on is that raw callsbacks should be wrapped in a promise or future, but whether a promise is supposed to be used as a monad (chain of .then calls) or whether its supposed to be used via special compiler support is still open. I honestly don't know. I would go with await because C# has adopted it with great success but it's also not something that can just be added to an existing language without rebuilding the entire ecosystem and thus causing it to be a bad career choice.
"The current interpretations of Section 230 have enabled online platforms to hide behind the immunity to censor lawful speech in bad faith and is inconsistent with their own terms of service. To remedy this, the department’s legislative proposal revises and clarifies the existing language of Section 230 and replaces vague terms that may be used to shield arbitrary content moderation decisions with more concrete language that gives greater guidance to platforms, users, and courts.
The legislative proposal also adds language to the definition of “information content provider” to clarify when platforms should be responsible for speech that they affirmatively and substantively contribute to or modify."
Can someone competently defend this not being used directly as a tool by Trump to prevent his deeply deeply harmful misinformation about the virus and other things from being censored?
First, the draft legislation has a series of reforms to promote transparency and open discourse and ensure that platforms are fairer to the public when removing lawful speech from their services."
Let me impart some wisdom, having taught myself to sew just about every possible fabric I could get my hands on chasing this particular dragon: Gloves will never work for consumer haptics. If you're putting fabric on the palm or under fingers you're doing it wrong.
I'm all for overfinger exo as long as I can 1. wash it and 2. it only needs to come in one size to fit the vast majority of people.
We've started a co-op like this to build cross platform spatial web apps (MMOs, metaverses, online virtual storefronts, etc). The project is MIT licensed but we're going after big contracts, especially trying to fill voids in the events and retail space. While things are being developed, everyone is living on a bit of runway contributed by one of the partners to make the project a reality.
