yur83838

yup, redundancies can be used to dismiss employees. The caveat is that you can't rehire for that role for a certain period of time. This is simply to avoid the problem of companies claiming random employees are no longer needed.

It is not uncommon for smaller employers to fire a manager, and hire a new supervisor though. Same job - different title.

I'm unsure if it's been challenged at the FWC - I doubt it would stand.

stackblitz

As a contrary point of view - I have a W541 that is provided by my enterprise overlord including all the virus scanner and corporate crap that comes with it on Windows. I actually quite like Windows, but I prefer to use the right tool for the job - which is often Linux. I boot into Linux (daily) without one issue at all - it all worked out of the box and I have no complaints at all.

The closest thing to an issue is the poor battery life - but this has been my experience with all laptops and Linux.

I can't comment on the W540, and I wonder if it is that different compared to the W541.

This isn't a cop out. Anything different and Facebook would be blamed for censorship. This is a difficult problem to solve. It's practically human nature to form a mob and group think. It's one of the first things that kids do in pre-school.

I think the only solution to this problem is education.

Would you say LLVM's pseudo assembly is also not a plus?

> wattage

energy / power. Both work in this situation.

people still need to cross roads

To counter this point, I knocked out a web app in Go recently in a few hours. I think the speed of development depends on your familiarity.

Having said that, I would suggest the GP try both. I'm keen to try my hand at Elixir soon.

You don't need a router, but it is much more readable with one.

You don't need middleware, but it is much more readable with r.Use(jwtVerify) then writing a deeply nested half router with logic.

If you're running a single endpoint, then the router is adding zero value.

The difference is in the network boundaries. I write most of my code as microservices, but it would be incredibly easy to wrap it all up into a single binary.

It's not uncommon for go code to have one binary for separate microservice functions (see OKLog). This way you can change between a microservice, or a monolith (ish) with a CLI flag.

I often see time.Parse as a common complaint - but my code is much more readable when I can see what the date format looks like, rather than trying to interpret the cryptic syntax which differs from language to language.

It's sure not perfect, and it's impossible to please everyone but I think it was worth the experiment.

> Go's refusal to embrace this is a huge pain point. Dep is a decent start, but without a community actually doing things like releases, changelogs, and all the other things that go into a solid ecosystem, it's a half measure at best.

Go has indeed embraced it and is working on `dep` the officially sanctioned dependency manager.

It's under the official golang github repository.