

This isn’t true, there are other features that “emit code”, that includes: namespaces, decorators and some cases even async / await (when targeting ES5 or ES6).
This isn’t true, there are other features that “emit code”, that includes: namespaces, decorators and some cases even async / await (when targeting ES5 or ES6).
This isn’t true, there are other features that “emit code”, that includes: namespaces, decorators and some cases even async / await (when targeting ES5 or ES6).
Here’s a good example: https://stackoverflow.com/questions/47363996/why-does-an-enum-transpile-into-a-function
fair enough :D but it does happen and there are reasons for that: https://stackoverflow.com/questions/47363996/why-does-an-enum-transpile-into-a-function
Not really, because this stuff also happens: https://stackoverflow.com/questions/20278095/enums-in-typescript-what-is-the-javascript-code-doing a function call always has an inpact.
Its really not, have you noticed how an enum is transpiled? you end up with a function… a lot of other things follow the same pattern.
It does, the “compiler” adds a bunch of extra garbage for extra safety that really does have an impact.
I guess we can take the overhead of rust considering all the advantages. Go however… can’t even.
The problem with compiled JS is that it doesn’t last long. Any piece of software written in the popular frameworks will probably not compile in 5 years because xyz dependency. There might be ways around it, but all annoying and not good. Some type of software really needs more assurances that “might compile in 5 years” because some people can’t afford to upgrade to the latest framework down the path due to size or simply lack of time.
📦 Zero Dependencies - Pure JavaScript, no build step required
This is really the best part. However the example does run a npm run build…
I would be great to have something that can be imported in a script tag like jquery and not something that requires npm and compilarion.
If you want to get the job (of publishing a blog) done fast, and move on, then use WP. If you want to mess around probably look at editorjs.io.
If you want to get the job (of publishing a blog) done fast, and move on, then use WP. If you want to mess around probably look at editorjs.io.
At least WP is free, Ghost is as “free” until you find out its only useful with the rest of the payed platform. editorjs.io is much better in that sense.
Yeah Microsoft for what’s worth does play ball, you can open complaints and they’ll actually read those and act fast. Google is a total pain to deal with, even if you’re on some type of google partnership they’ll not do much.
It’s also good to make notes on every configuration setting.
I do save my settings for the various programs in a git repository…
If it need documentation means things are over the line when comes to complexity and I should scale down / simplify. :)
Complexity and over-engineering are a serious problem, I really try to keep it as simple as possible so I don’t have to waste time managing it, dealing with updates and potential security issues. Simple code/infrastructure breaks less and has less potential insecure points.
Unless someone finds a way to advertise nodes that doesn’t depend on the entry point then yes. Consider this example: https://github.com/bitcoin/bitcoin/blob/1b2460bd5824170ab85757e35f81197199cce9d6/src/chainparams.cpp#L112 if someone takes down those domains it is game over for a new node until someone updates the code.
I get your point, those systems make it harder to take down things permanently but they aren’t as resilient and perfect as people paint them to be - an it has nothing to do with being pedantic, it is just the reality of things.
Welcome to modern operating systems, apps, browsers, websites… just buy a high-dpi 30" screen :D