kking50

It's not a new golden age of fitness. There may be a short-term boon, but people's motivation will eventually nose dive without social interaction.

"Previously, 50% of gym-goers quit after 6 months." Why would you not expect the same thing to happen with people's quarantine workout motivations? We're still within the first 6 months of quarantine.

I feel like part of the reluctance with accepting C# and .NET as fully open source platform, outside of the Microsoft ecosystem, is somewhat due to Azure. At the moment, the three main cloud providers basically vendor-lock you. There's no great standard body controlling cloud providers at the moment. Sure Terraform tries it's best to provide cross-provider APIs, but it's not the same as a standard. As such, most companies that pick .NET will pick Azure. Then developers are right back into the feeling of the old-school Microsoft proprietary vendor-lock.

I feel relatively similar about Visual Studio. It's pretty clear that it's a 2nd class citizen on Mac due to being build on top of Mono. Java apps built on the JVM feel pretty much the same whether on Windows or OS X. Mono on the other hand...it just feels like a monkeypatch. I think porting things from Windows to OS X is tough because OS X has so much foundation in UX whereas even new Windows machines are still behind 2009 MacBook Pros. This just makes Windows apps ported to OS X feel sluggish to me (and many of the features are stripped). Purely opinion.

I'm actually trying .NET Code and Visual Studio in a professional setting for the first time and I'm not hating it. WSL is what originally put Microsoft back on my radar and I'm starting to take them more seriously these days.

I quite appreciate these kinds of posts. Fun and silly, yet make you think about the way computers work outside the box.

Read the ECMA scripts. ESPECIALLY sections 13 and 15. Seriously, even the best textbooks will only give you a superficial understanding relative to the actual standards. Sure there are different JS engines, but they all do roughly the same thing. Master the algorithms in the ECMA standard and you won't even need to read textbooks. You will be able to deduce and derive those concepts yourself.

Understand exactly how JavaScript gets converted under the hood. Remember, ECMA could be implemented in any language not just C/C++. What you're looking for is algorithmic understanding.

For example, here's the snippet that explains how "new" works in JavaScript https://www.ecma-international.org/ecma-262/5.1/#sec-15.2.2..... Going through the algorithm, your first thought may be "wtf is [[Prototype]]"? Dig into it. Understand when, where, and how [[proto]] and __proto__ get assigned. Learn about the cyclic references that allow everything to be an object including functions.

Of course, feel free to use external resources to assist you while reading ECMA since it is quite dry. For the example above, this amazing Stack Overflow post can help you visualize the algorithm: https://stackoverflow.com/questions/650764/how-does-proto-di...

Nooooo! Don't make me INSTALL a standard-compliant shell!! Make me install a NON-standard-compliant shell.

It's better to have an old version of a standard-compliant shell be the default. Users can easily install the latest bash/zsh, but make that a personal choice.

The license isn't a valid reason to swap out bash.

Nooo don't make zsh the default shell. Wtf is Apple doing?

I don't have an issue if people want to use/download zsh, but making it the OS default is a huge mistake! From the zsh docs themselves:

"Broadly, bash has paid more attention to standards compliancy (i.e. POSIX) for longer, and has so far avoided the more abstruse interactive features (programmable completion, etc.) that zsh has." ~http://zsh.sourceforge.net/FAQ/zshfaq02.html#l14

Don't make a less-standards compliant shell the default! Bash is one of the few programs I can rely on between all my different devices.

I've found that people who stay up late also tend to tell you [edit: and brag] about it. For example, if a friend is out late partying you're almost guaranteed to hear about how late they stayed out the next day.

I think it goes both ways because people want to justify why they are not at 100% energy. Partly to not offend others when you're being abnormally unenthusiastic. A type of social defense mechanism.

Curious how that's a security issue? Bookmarks are just public links, so there's no problem if someone sniffs them out, right?

Do you mean if a site stores cryptographic information in the url? Or is it the act of syncing with your local machine that introduces surfaces of attack on your local system?

I respectfully disagree with that last part. IMO it's your moral obligation as a distributor of information to, to the best of your ability, ensure its' truth and validity.

I'm not saying it has to be PhD-thesis-level, but if proven wrong you are morally obligated to update the information or remove it. Otherwise you are spreading false knowledge. This doesn't apply to opinions ofc (the bulk of private blogging).

Screw entitled users though, they should fix it themselves :)

Had a guy interviewing for an intern position once say, after my coworker showed him a bit of code, "the biggest file I saw today was 500 lines, so I'm pretty sure I can handle it. I'm used to working on PHP scripts with thousands of lines. Now that's scary." He lost my vote in three sentences.

"However, out of this wonderfully frustrating evolution of JavaScript I think things are beginning to settle down."

React - first commit May 29, 2013

Flux - first commit July 23, 2014

ExpressJS - first commit July 31, 2012

RethinkDB - first commit Oct 3, 2009

Yeah, I doubt it.

Giving an option is an awesome idea! It says a lot about the flexibility and open-mindedness of your company. Too many companies have a "take it or leave it" interview processes.

IMO it depends on the position. I did a test-project with a follow up code review for my first job and it was a fantastic. If I had not gotten the job, I still would have been happy with the experience and code to show future employers.

If you are interviewing for a more junior or senior position, many candidates are probably switching jobs and are already swamped with work. Also, they probably already have some pet projects they can share. Requiring a test project may seem amateurish.

Had the same reaction. How is this on the front page of HN?

I love lightweight frameworks that exist mainly to reduce boilerplate code and, for web development, mitigate cross-browser compatibility issues. ExpressJS and jQuery are good JavaScript examples.

I tend to avoid frameworks that attempt to push developers into coding "the framework's way" (cough cough AngularJS). Such frameworks are often great in the beginning, but once you pass the basic application stage, a deep understanding of the framework itself will become necessary and it will stop saving you time. Sometimes you have to adapt special ways of writing tests, debug nonsensical stack trace dumps, etc. Not to mention it increases the overhead of bringing new developers on the project.

tl;dr Don't use heavyweight frameworks unless you have a good reason.

Here's a more aesthetic version http://www.html5rocks.com/en/tutorials/internals/howbrowsers...