The author of this post is complaining about CSS-Tricks not getting paid.
If the person who works ("works") for Digital Ocean but is not getting paid, should pretty leave immediately if that is the case. :) I.e, demanding on some moral premise that this other guy who I don't like is getting money, is quite a "far-left" way to go about it.
The author of the post (Vale) is talking about how the editor of CSS Tricks (Geoff) is not being paid by the owner of CSS Tricks (Digital Ocean)
This is not the first issue since Digital Ocean acquired CSS Tricks.
I’d encourage you to educate yourself more on the situation instead of discounting people as “far-left” (whatever you think that means in this context)
Well, the post is calling David Heinemeir Hansson "far-right". I'd instead encourage him, and perhaps you, to educate yourself on what that means, then read up on his blog post(s).
Here’s a section from the Wikipedia page on far right politics:
> Key to the far-right worldview is the notion of societal purity, often invoking ideas of a homogeneous community based on cultural, ethnic, national, racial, or religious lines or a combination of them
It sounds like DHH is talking about “societal purity” and is “invoking ideas of a homogeneous community based on cultural, ethnic, national, racial, or religious lines”
If he is, then that sure seems like far right politics to me.
Right, but DHH's argument isn't about cultural homogeneity for the sake of it, but rather the consequences of what the other cultures have brought. Reading further from links from the blog, either to his other posts, to the Tommy Robinson march, etc., would tell you that. I.e, you conflate race with merit - because they do associate in the statistics sense, but one is not the other.
The OP on the other hand demands funds from a private company, main argument being that "this other person, who I don't like, got money, then a website I do like, should too".
I don’t really want to argue with you about whether DHH is far right because it’s tangential to the main point of the article and based on your response I don’t think we’d agree.
It’s not about “giving money to a website” it’s about the fact that Digital Ocean purchased a business and hired an employee and then ghosted that employee and stopped paying them (without firing them or shuttering the business.) Thats messed up
While unfortunate that the website is inactive, then any employer is pretty much free to let go any employee (and the employee dispute this if they have grounds for it from contracts). Not to circle back to the left/right topic, but if you think this is "messed up", then I'm not sure how you think the world works at all.
If the love for that site is so great, I'm sure someone will pick it up. Otherwise, I'd doubt "size of love" we are talking about here.
The name works fine in the browser, but since jest/enzyme use node to run tests, I had issues with functional components (defined as arrow functions and immediately exported) were missing their names.
Mostly because instead of using the DOM and a general purpose renderer (Blink), Sublime's text editor component is actually an OpenGL canvas made specifically for that.
That's not why Atom feels slow. You're running a machine that can run JS faster today than any machine could run C 10 years ago. There haven't been any major innovations in text editor technology in that time, none that would warrant such a huge slow down.
Atom feels slow because it's over engineered. They try to make everything run through the plugin system.
The point is not if JavaScript is fast or not (which btw it isn't faster than C++ or not even just as fast), but how many layers of abstraction JS has to go through to display stuff on the screen or do anything useful. Having to fight with DOM and CSS to do anything like syntax highlighting is effectively triggering execution of millions of lines of code compared to sublime text that does a raw win32 or Cocoa call.
Comparison with 10 years ago is also not so relevant. 10 years ago you didn't try to autocomplete through an average modern JS project where thousands of files are created on disk even before you create your first div. Data processing needs are outgrowing CPUs improvements by far.
IOW there's no way Atom is getting as fast as Sublime, because of the huge stack it is built upon. It might get fast enough though, but my feeling is that the discrepancy is actually getting bigger rather than smaller, as we evolve our average needs as programmers
There are more ways than just the DOM to render text. And I didn't claim JS was faster than C, I said JS on modern hardware is faster than C on 10 year old hardware. Yet we still managed to run text editors "fast enough" 10 years ago. Finally, I made the specific point to say that Atom is not a good example of what should be possible in JS.
