Hacker Newsnew | past | comments | ask | show | jobs | submit | cbeach's commentslogin

Once again, Eurocrats gaslight the public into accepting dystopian surveillance and control mechanisms.

They love to make Trump a boogieman, too.


as useful idiots go, he’s surprisingly versatile

I’m in the UK. There is strong anti-ILLEGAL-immigrant sentiment, because hundreds of thousands of undocumented men originating in Africa and the Middle East have illegally crossed the English Channel from France and then made asylum claims, meaning the UK taxpayer is forced (by treaty) to house them and feed them. These are quite evidently opportunists. A large proportion are young fighting-age men, and most are fleeing countries where there is no current conflict.

As a taxpayer in a cost of living crisis I resent seeing hotels full of these chancers.

And I don’t think women and girls are safe with them around, given the staggering sexual crime statistics

https://www.migrationcentral.co.uk/p/up-to-third-of-sexual-a...

Call me “anti-immigrant” if you like. I don’t care. I’m voting for fairness and safety in the next election.


I'm not really interested in your personal opinion about immigration. I don't really know why you decided to vent your personal grievance at me.

Someone donate to this guy so he can upgrade his 20 y/o Thinkpad!

Scala is a fantastic language and in fact I'd say it's the language that proves the article wrong.

Java was the language where "write libraries instead" happened, and it became an absolute burden. So many ugly libraries, frameworks and patterns built to overcome the limitations of a simple language.

Scala unified the tried-and-tested design patterns and library features used in the Java ecosystem into the core of its language, and we're better off for it.

In Java we needed Spring (urghh) for dependency injection. In Scala we have the "given" keyword.

In Java we needed Guava to do anything interesting with functional programming. FP features were slowly added to the Java core, but the power and expressivity of Java FP is woeful compared what's available at the core of Scala and its collections libraries.

In Java we needed Lombok and builder patterns. In Scala we have case classes, named and default parameters and immutability by default.

In the Java ecosystem, optionality comes through a mixture of nulls (yuck) and the crude and inconsistently-used "Optional". In Scala, Option is in the core, and composes naturally.

In Java, checked exceptions infect method signatures. In Scala we have Try, Either and Validated. Errors are values. It's so much more composable.

There's so much more - but hopefully I've made the point that there's a legitimate benefit in taking the best from a mature ecosystem and simple language like Java and creating a new, more elegant and complete language like Scala.


I think you misunderstood the article (or only read the first couple paragraphs). The author sets the stage with the statement in the article title (a quote heard from other people), but shows that those fancy language features in some languages are exactly why rich, easy-to-use libraries can be built. And that some of these rich, easy-to-use libraries simply cannot be built in some languages that lack those features.

So you don't actually disagree with the article.


> the language that proves the article wrong

It helps to actually read it. The title is in quotes because the point of the article is to refute it.


Thanks for including the context in the title.

RIP, Joe


> Much better solution is to help you junior dev solve the problem

Meanwhile there are five other subordinates and all the overhead that you're neglecting while you fiddle with your dev environment trying to get started on the task, as you've been away from direct engineering for a while.


The simulator is an excellent reminder that engineering managers sign up for an eternity in the Kobayashi Maru scenario, and there's no way to Captain Kirk it, either.

https://en.wikipedia.org/wiki/Kobayashi_Maru

I've had the fortune to be able to steer my career back down to IC with no loss of income every time I have been pushed up into an EM role.

Only one data point, but I'm 100% happier as IC than EM.


Glad that you chose happiness.

But there are other players who likes to trade it for Money!

Thanks for sharing the Kobayashi Maru scenario though! Can use it as a fun simulation if someone fails all scenarios to make it light hearted yet meaningful.


> Punishing in public

The junior dev is watching, and got the benefit of seeing that you value his time

> managing via Slack

Far preferable to arranging a face to face meeting over this low impact, simple procedural issue

> being a speed bump just because

Defending your team's finite attention and time from random direct requests from the business is a major part of your job as an EM.

> "scope creep" bogeyman

There's good reason scopes are defined and communicated, and deadlines and expectations are managed.


> far preferable to arranging a face to face meeting over this low impact, simple procedural issue

Whenever an issue involves people, slack simply won't suffice. There's too much good will lost on either side. "No worries if not [grumble grumble]!"

This isn't procedural, like sending an invoice to the wrong email address. This is a vp overstepping and threatening the success of another employee. They know what they're doing.


Id agree if it were a VP of Eng (total mess) or Product (should know and be bought in on the dev process) but this is a VP of sales. Depending on the company they can be much more operational and I would just assume that they asked the individual due to familiarity or happenstance and didn't understand the level of effort to deliver.

Quickly understanding the urgency/importance of the ask while communicating the impact it is having on the deliverable is the right call. Good business people work like this all the time. Seeing the discussion is a good learning opportunity for a junior.


The US casually eliminating a nasty despot is likely to have a chilling effect on the other nasty despots.

Putin and Kim will -not- be emboldened by this act - quite the opposite.


If only this were about eliminating a nasty despot…

Whatever innuendo you'd like to apply to Trump's action, Maduro is objectively a nasty despot.

Maduro was a monstrous dictator who was guaranteed to kill more people than this US strike did. And there is an opposition party which has been suppressed by Maduro, but is otherwise ready to go. There is much hope to be had for this beautiful country and its people now.

Hopefully this act will also have a chilling effect on other vile left wing dictators like those in North Korea and Cuba


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: