w3news

7 ms·

1.
by w3news 10mo ago
Thanks, I use JSDoc for several years, and also validate it with Typescript. So I just write plain Javascript with JSDoc, with no build step. Typescript only validates the types, and not transforming the code. Did you also know that you can
2.
by w3news 11mo ago
Microsoft just fork Atom, and Atom had already good and a lot of extensions. Before Microsoft buy Github, there was no reason to switch to VSCode instead of Atom. When Microsoft buy Github, it received Atom from the Github team, and Microso
3.
by w3news 1y ago
Next.js is indeed not very open for feedback. Next.js is also opinionated. So if you are using Next.js, you can use what they have and do it their way. If there is something, just wait... For me, it isn't a framework I want to use in a
4.
by w3news 1y ago
To be a better programmer, write little proofs in your code. We call that tests and types, proof that it should do what you expect. Especially when writing tests first, then types, then the code. Start with a test per acceptance criteria, t
5.
by w3news 1y ago
I remember that I did the same in 2005-2006, just combine XML with XSL(T) to let the browser transform the XML into HTML. After that, also combined XML with XSL(T) with PHP. At that time modern way of working, separate concerns in the front
6.
by w3news 2y ago
Emission zone shouldnt be the issue, it is about the amount of cars and road safety for every user. Check e.g. the Dutch road design, where many kids ride bikes. This is already for decades, and has nothing to do with emission zones. But
7.
by w3news 3y ago
When you build an API, please start with the OpenAPI specification, before you write any code for your API. It can be iterative, but for every part, just start with the OpenAPI, and think about what you want from the API, what do you want t
8.
by w3news 3y ago
I like the idea, think about what you really need, keep it simple. I also try to move centralized computing to decentralized computing more and more. And that can also be done to let the client do more computing. And also storage, is it nee
9.
by w3news 3y ago
So true, we build large complex frameworks, abstractions over abstractions. Try to make things easy to build and maintain. But I think the problem is that many developers that using these frameworks not even know the Javascript basics. Of c
10.
by w3news 3y ago
Too mad that we have to hack our car to customize it. We can reinstall computers very easy, choose the OS you like. But cannot do something on our car. Old cars, you can modify everything, grap your tools, and you can do what you want. Mode
11.
by w3news 3y ago
I love to build extensions. Such a nice thing they made website source easy to read and manipulate for your own usage, and can even share your modifications to build an extension. It is just like your newspaper, you can write on it, cut pre
12.
by w3news 3y ago
There is a standard for browser extensions. I build also browser extensions before the standard. So you can build now a browser extension that works in Chrome, Firefox, Edge and Safari. But indeed, you can also use some specific api's
13.
by w3news 3y ago
Good old times, when the web was simple, and more decentralized
14.
by w3news 3y ago
ESM is a defined default you find back in ECMA specifications. That is why everybody should migratie. Node.je is also moving ESM to the default. If some systems dont do it, dont use it anymore. That it went i dont use jest anymore, and Node
15.
by w3news 3y ago
That it why i use native functions. No typescript syntax, no jest. For testing i use just the native test runner, and that works great with ESM. Jest has indeed still not good ESM support, you can do some Babel trics, but makes the process
16.
by w3news 3y ago
Why not using Node how it is designed, than ESM works great. For type checking on development, you can do it with ESLint and JSDoc in Typescript modus. You have the same type checking like you have in ts files. You can even import types fro
17.
by w3news 3y ago
I was expecting nearly 100 Linux versions, but wow, it is even 100 if you just count all Linux versions as a single OS.
18.
by w3news 3y ago
It is type safety at runtime. Typescript gives you some type safety at develop time (like jsdoc also can do) But if I read it right, this helps you to generate OpenAPI spec to validate the api endpoints, to get easy type safety at runtime.
19.
by w3news 3y ago
Typescript wil not help, you can create the same mass. What me helped is to write almost all code functional and not oop. Every method had just 1 way data can in and out the method, no side effects. Classes have a lot of flexibility that ma
20.
by w3news 3y ago
Funny thing is that a lot of developers like that JavaScript received class support, and makes it easier to write oop. Many people dient understand 'this' in JavaScript, and ways are created to reduce the usage of 'this'
21.
by w3news 3y ago
Why need another dialect if you can just use Javascript. I think most people don't really know Javascript, and what is possible. Most arguments to use Typescript are not good arguments, and Javascript can more than most people think. T
22.
by w3news 3y ago
I think, if you write server code / command line apps. It is better to choose for Javascript over Typescript, so you don't have the translation, and you know the system where you running on, and you can build for that Node version
23.
by w3news 3y ago
I always say, Typescript is no language but a dialect. JavaScript is the official language that will used in production. You can talk in a dialect, but for official things you have to write and talk the official language. Always think if th
24.
by w3news 3y ago
Isnt this make it possible to write easier bad designed code structures?
25.
by w3news 5y ago
JS: [b,a] = [a,b];
26.
by w3news 5y ago
No, you don't need a build system, but most developers cannot work anymore without a build system. And what about node.js, it's a lot better to skip a build step. I think typescript is a temp hype just like jQuery, useful for many
27.
by w3news 5y ago
It shouldnt, the concept of an EV is simple, but car companies add to much gadgets. Just look to electric remote toy cars how simple the basics are for an EV. Lets make EV cars just as simple as electric toy cars. Keep it simple, dont make
28.
by w3news 5y ago
Indeed, i had also a Golf (TDI) from 2005, very reliable car that works always, it is simple and everybody can repair it. Why cannot they make EV's that are simple, we dont need all the gadgets that will break.
29.
by w3news 5y ago
This is indeed not limited to EV's and cars. Search e.g. on "John Deere right to repair", and you will see that farmers cannot repair their own tractor anymore, and need the factory dealer to repair it, and the owner have to
30.
by w3news 5y ago
Indeed, don't forget the developers of free and open source software that is used for your website, and also share some useful generic code for free.

More ›