4,257 karma · joined January 27, 2009
Genuine questions- I don't really understand
At a high level, the current administration is seeking ways to cut tax for the wealthy and pay and conditions for workers. As a property developer, Trump has a literal vested interest in maintaining high property values.
Its really difficult to see how this will translate into more affordable housing for poor people.
Is there any compelling reason not to just compile TypeScript to WASM? Why should it have JavaScript as its compile target?
Some organizations that are deeply invested in a given tech provider do it anyway, but this is gradually going away.
I'm 30 years in now, and on balance, whilst they have clear advantages, I'm still not convinced that typed languages are essential, particularly for low level or module programming.
Its ironic therefore that when an impoverished Scottish single mother, JK Rowling, wrote the most successful childrens books of all time in the ´90s, that they centred on wealthy kids who went to boarding school.
But yes- you could bundle less, but that would be a disadvantage, particularly if a bundle suddenly fails and you don’t know which change caused it. But maybe that’s not a big deal for your use case.
The fix would then have to be some variation of:
a) Stop testing (so often)
b) Stop bundling before testing
c) Publish to a different package manager
- all of which would affect the overall quality and quantity npm modules.
Its not always obvious who has the most important use cases. In the case of NPM they are prioritizing the user experience of module authors. I totally see how this change would be great for module consumers, yet create potentially massive inconvenience for module authors.
Interesting write-up
Never thought of it like that before
The question (not addressed in the article) is: is there in fact a gigantic, widespread problem of using cache-sniffing to fingerprint users?
We have always known that this was possible, yet continued to include cross site caching anyway because of the enormous benefits. Presumably something fairly major has recently happened in order for this functionality to be removed- if so what?
What is the actual problem thats being solved here? Is cache-sniffing being actively used for fingerprinting or something?
Whats going on here?
A lot of these "improvements" fall into the following 3 categories:
1) More complexity around issue tracking
2) More complexity around permissions
3) IDE-ness and general visual-studioification of the web interface.
Since many of the issues make GitHub bloated and more difficult to use for general use cases, they _should_ be removed.