falafel
falafel on Hacker News
BBC, NPR and Washington Post are all left leaning organizations funded by governments and billionaires. I don't know if I would call this "getting a reasonable overview of world and local news".
I like Angular and I think it's still a solid choice for new apps in an enterprise setting, and signals are a welcome addition that solve real problems, but I don't understand the hype. Signals are as old as JavaScript if not older. The diamond problem and sync propagation are not new problems. We've come full circle. Old problems become new problems but with the same solutions. What did we gain with all of these iterations if we landed back on what was essentially the Knockout model of 2010?
I'm reminded of papers such as "Deprecating the Observer Pattern (2010) [1]" which documented solutions to these problems a long time ago.
[1] https://www.semanticscholar.org/paper/Deprecating-the-Observ...
do-notation can be easily implemented using delimited continuations (ie. generators). Generators compose well and flatten tail calls so you don't need TCO or trampolines. The only notable issue is that one-shot delimited continuations like generators don't work with non-deterministic monads (ie. List). Multi-shot can be emulated by keeping a cache of past values and replaying the generator, but performance will suffer. See burrido [1] for a JavaScript do-notation implementation.
[1] https://github.com/pelotom/burrido
There isn't much difference nowadays. I think it's just a matter of preference as long as the trackpad is made of glass, which aren't hard to find on PC's anymore.
I even prefer my PC trackpad on Linux vs my Mac trackpad on macOS because on Linux there are many more settings I can configure to get it working exactly to my liking.
Personally, I don't like the cursor acceleration profile in macOS by default. You can change certain values through the terminal, but the Synaptics and libinput options on Linux are way more in depth and packaged in a nice GUI (at least in KDE Plasma).
So the employer punishes people that cannot afford to live close to the office? And on top of that, if they need to travel to conduct business, their pay is decreased? If I understand this right, it seems like a horrible idea, and I would not want to work at a place like that at all. If the company needs to hire talent that lives far away, why should they be punished?
That's not the comparison as far as I understand it. The analogy is of someone that dedicates all their time to becoming the best at their craft, like Chopin. It's not about being a genius.
I don't agree with the first two points. Native applications aren't consistent in this way. There are dozens of cross-platform GUI kits and they all behave slightly different, just like Electron apps. If you want consistency, you need to build multiple apps, one for each OS with their respective toolkits. Ain't nobody got time for that when you can easily build on Electron and target browsers, macOS, Windows, and Linux in one single app. No wonder Electron is winning the battle so far, regardless of your last point.
It is indeed ironic. I was initially interested in the content, but I closed the site in less than a minute after getting frustrated by the emojis, blurry text and annoying sidebar and header animations when scrolling.
I remember another site with similar content and also pretty annoying UX: https://lawsofux.com
I'd take a long markdown document with a table of contents over this any day.
I'm still interested in reading about these UX principles though. Is there another alternative, easier to read resource?
Chief Architect.
About 15h per week, or almost half my time basically.
* ~1h daily for status meetings
* ~2h twice a week for project coordination and discussion
* ~4h once a week for overarching architecture decisions across all projects
* Various other 30min to 1h meetings depending on the week
It's terribly inefficient, but I cannot change it; believe me, I tried.
As a remote employee, I fully agree. Also, can we stop polluting the environment unnecessarily? There are too many cars on the road with just one person inside. How many of those people really need to commute into an office every day because the job requires it?
> places outside of North America and West Europe have lagged in attitudes to software development.
This is right. From my experience working with an offshore team in India, the main problem is cultural. A large majority of the developers in India I've worked with have no interest in furthering their development carrier, but see it simply as a way to transition into management as fast as possible. In practice, this means that you can go from a junior developer to a project manager in the span of 2 years or so. 2 years is not enough time to solidify your knowledge and become the t-shaped programmer that this industry requires. I think one needs at least 5 years of work and experimentation in this field to reach the level where you can contribute positively to a company, without creating huge amounts of technical debt.
To be honest, I think if anything the trend will continue and the salaries will go up. There will still be a shortage of highly skilled developers who demand higher salaries. At my company we've been trying to hire a senior frontend developer for the last 6 months; it's hard, especially outside of major tech areas. Most people come unprepared, lie in their resumes, and suffer intensely from the Dunning Kruger effect. I don't see this trend of lying to get the job that pays good money to stop anytime soon. Out the 1.6M programmers employed in the US, I think a large portion still have the job because companies are desperate to hire, but don't know how hire for this industry.
Also what's shocking is that you see plenty of young able people in those tents that could get a job yet decide to stay there. That baffles me. If you have arms, and legs, and you're doing ok in the membrane, then you can find a job in this country.
Callback hell? What is this 2010? Callback hell is a non-issue in modern JS code with promises, and async/await.
They haven't unfortunately. npm 5.5.1 is still very broken, especially if you use postinstall scripts.