I continue to be baffled and amused by the complete meltdown of the typescript community over the actions of a single man on a single package. The only people who have legitimate gripes are those that had been actively contributing and whose work was erased. The rest of you are acting absurdly childish. The anger and vitriol being thrown at anyone who disagrees on how to write javascript would make me embarrassed if I was associated or involved in the ts community.
"There are only two kinds of languages: the ones people complain about and the ones nobody uses."
Web & mobile development took a wrong tern 10 million miles back, and no one wants to turn the car around and admit it.
SPAs are mostly garbage, and the internet has been irreparably damaged by lazy devs chasing trends just to building simple sites with overly complicated fe frameworks.
90% of the internet actually should just be rendered server side with a bit of js for interactivity. JQuery was fine at the time, Javascript is better now and Alpinejs is actually awesome. Nowadays, REST w/HTMX and HATEOAS is the most productive, painless and enjoyable web development can get. Minimal dependencies, tiny file sizes, fast and simple.
Unless your web site needs to work offline (it probably doesn't), or it has to manage client state for dozen/hundreds of data points (e.g. Google Maps), you don't need a SPA. If your site only needs to track minimal state, just use a good SSR web framework (Rails, asp.net, Django, whatever).
Meanwhile PHP quietly runs 80% of the internet by being used for WordPress.
Yes, and the people directly contributing to the project have legitimate gripes. Although, the parable of dhh is if you get on an asshole scorpions back, don't be surprised if you get stung. Dudes been an unreasonable prick for nearly 20 years now.
My comments directed at the manufactured outrage from the tooling zealots incapable of having a mature conversation. Or even accept a difference of opinion. The number of comments that start with, "never heard of Turbo, but let me weigh in on why you're an idiot for not liking Typescript. " is very telling...
Seems it got much worse.
Seems like it's going great for the developer.
considering how huge FB still is.
FB is only huge because they've expanded all over the globe, even providing internet to developing nations to facilitate new user acquisition. In reality they've been bleeding the original Western users that signed up between '04-'10, and growth among new generations flatland a long time ago. There's a reason Meta aggressively expanded to other ventures (or attempt to create platforms) like Instagram, Threads, what's app, VR and metaverse. Metas only chance at sustainable growth and capturing young people is to build or buy platforms young people will use, because it ain't Facebook.
Or federal funding.
America's two parties are Regressives vs Conservatives.
I was there for the first wave of SPAs, I even learned angularJs and Knockout. It did feel like a major atep forward, being able to make highly interactive applications. However, things quickly went off the rails when the tools stopped being about managing heavy client state, and became the default for everything, even when it ment using JavaScript to build extremely basic functionally browsers did natively with html, but extremely worse(e.g. navigation). The modern Web really is a victim of hype and trends.
Unless your app needs to work offline, or you have to manage dozens of constantly changing client side data points concurrently, your site doesn't need to be a big heavy js framework. My rule is if it looks like Google Maps, you need a SPA. if it looks like Gmail you need REST/HATEOS. and if it looks like google's mainpage, you need a server side rendering.
At some point you might see the light, and go back to making your websites simpler, but Im not hopeful. Until then I'm building the majority of things with HTMX and alpineJs.
Always remember, the silicon valley ethos of "break things" wasn't about their applications, it was about breaking industry, society, laws and your ability to oversee or regulate them.
I thought it was a balance between new shows getting better engagement than old shows, and contracts lasting 3 seasons, which required re-negotiations in favor of the talent. Basically a business model hyper-focused on subscriber growth metrics instead of subscriber retention.
I'd use what I've been experimenting with exclusively on personal projects: htmx, AlpineJs and Razor Pages on PostgreSQL AKA the HARP stack. Obviously, a hilarious acronym was needed.
Which might sound esoteric and hipster, but I'd contend it's pretty close to how we were building websites for decades before the cult of the SPA took over. For those not in the know, HARP is built with no fe frameworks, everything is rendered server side and html is swapped in the DOM on the fly. Htmx is a very tiny js library that makes backend requests to the server, and renders the returned htmx within the current page. AlpineJs is a client-side js library that acts like a modernized and simplified jQuery. Razor Pages is part of the ASP.NET web framework that runs on .Net, and produces html from Razor templates coded with C#. My professional work is on SQL Server, but I like PostgreSQL as the runner up because I'm not paying mssql out of my own pocket.
I'm wouldn't be concerned with hiring since I'd mostly just need C# developers with some designers. .Net developers are a dime a dozen, and many are seasoned vets with 15+ years experience building with .Net. It's easy to build a career with just C#/.net/asp.net so few of these devs are running around flipping frameworks every few hype cycles.
But I might have just shown my age and bias.
6First off, Inheritance is not "dead". We all just learned to favour interface inheritance over class inheritance.
Secondly, class inheritance is not bad or useless, it's just poorly taught and wildly overused. The fact that the article still uses the bullshit Animal kingdom example is indicative of that. There's no value in trying to model cats and dogs in OOP.
Inheritance is pretty useful in niche scenarios, mostly involving polymorphism and probably in the context of Library or Framework code. Trying to re-use code between classes with inheritance is always the incorrect approach. Two classes that are unrelated but have similar properties don't actually need a common base class, they can each have their own version of the data.
The big, big, big problem outside the education system comes back to the top down, design-first approach. There's still this strange practice of trying to model class hierarchies and abstract classes in neat little diagrams before you've actually started writing code. No UML type document has ever survived contact with the real world. If you need any form of inheritance, it will become obvious as you build out your system.
In a 4-D chess move, by canceling everything with no resolution, they've made their shows not worth pirating by making them not worth watching.
Apparently every code base I've ever worked on was run through this.
Some of us have had to support multiple database targets. So I don't know about changing a database in a running application, but a good abstraction has made it easier to extend support and add clients when we could quickly and easily add new database providerz
I never saw that, that's legitimately funny. I'd love to be in the room when that feature was designed, and the reaction of the developer it was handed too.
This is the correct comment.
Martin Fowler called them sociable tests. The only way to properly test your units' behavior is to pull in their dependencies. Isolated tests are useless, brittle and slow to write.
It's a form of Black-Box Testing, essentially you want to validate expected behavior. Implementation can change, but your outcome should remain the same.
This is a big target for Test Driven Development, since your first step is to write the test with the expected outcome, then you write the most basic implementation, and when you can verify the behavior, then you are free to re-factor to improve implementation knowing your test will tell you if the behavior changes with each internal change.
Having watched the video, I can confirm it is a terrible summary. The point of the Fireship 'Code Reports' is to be a light hearted summation of the news.
The video is hilarious, with tonal and visual gags that are simply lost in translation to text. You might as well just scan the home page to get the acctual news.
I don't know if the game is the best example of busineses making top-down design decisions, since that game was an obvious scam from the start.
I find ORMs exist best in a mid-sized project, most valuable in a CQRS context.
For anything small, they massively over complicate the architecture. For the large enterprise systems, they always seem to choke on an already large and complex domain.
So a mid size project, maybe with less than a hundred or so data objects works best with an ORM. In that way, they've also been most productive mainly for the CUD of the CRUD approach. I'd rather write my domain logic with the speed and safety of an ORM during writes, but leverage the flexibility and expressiveness of SQL when I'm crafting efficient read queries.
I just assumed everyone here suffered from Acute Gastrointestinal Illness
Wild swings between the greatest trip you've ever had, and excruciatingly slow death.
I didn't have an answer for a very long time. Or more seriously, the answer was "the one that paid the most". I've run the gamut of popular languages, C, C++, Java, Javascript, perl, ruby, Python, Visual Basic, VB.Net, C# and F#.
But the last couple years it's really been C#. The pace of development on the language/runtime has really picked up with yearly releases. The features that are added and iterated on are expressive and intuitive. You can tell from the discussion posts on how a feature is being considered for inclusion is thoughtful and deliberate. It really feels like the language is in good hands.
Just wish those hands weren't Microsoft.
To list some good ones that haven't already been ssid:
Stop podcasting yourself
A problem squared
Secretly Incredibly Fascinating
the tests are now larger than the thing itself
Is such a weird complaint. You should aim for your codebase to be as small, simple and readable as possible, while your tests should be a specification that guarantees behavior is consistent between refactors. When you add behavior, you add tests, when you remove a behavior, you delete tests.
The size of either is independent of eachother. Small code bases that provide lots of features should be simple to read, but with a lot of tests.
Like a fungus you learn to live with
Yes, I couldn't recommend htmx highly enough.
The company I work for is smort
This is every company I've ever worked for. If other people didn't vouche for their own tests, I'd assume automated testing was a myth.
You can write it in whatever language you want, as long as it's rust.
/s
Ignore the weird tribalism over the languages other people prefer to use.
Just one thing to keep in mind about VB.Net, Microsoft considers it "done". Active development is done, yhe language won't receive any new enhancements anymore, so all the cool new C# features (like pattern matching) will not be back ported to VB.Net.
I've programmed C# for nearly 15 years, and have used goto twice . Once to simplify an early break from a nested loop, essentially a nested continue. The second was to refactor a giant switch statement in a parser, essentially removing convoluted while loops, and just did a goto the start.
It's one of those things that almost should never be used, but the times it's been needed, it removed a lot of silliness.
Razor
Razor is the templating engine that's been there since the original MVC. Blazor Server is the one that needs a server and streams changes to the client using signalR. Blazor WASM is the one that uses Web Assembly. As of .Net 8, Blazor can now also ne used as a generic SSR backend. They all use Razor Components, which is a component model using the Razor engine.
Not to be confused with Razor Pages, which is also a generic SSR backend.
The sad truth is Twitter actually DDoSing itself.
Oh wow, I've seen this guys shorts start popping up constantly. He seems like he understands the algorithm enough to explode
What do you mean going to? Internet Explorer supported VBscript, which was a "competitor" to Javascript. Though being locked to ie was a hindrance to adoption. That, and it was based on vb.
Remember when people were calling this dummy the "real life Tony Stark"? Lol.