HN user

one2three4

451 karma

Big in Japan

Posts32
Comments71
View on HN
www.welcometothejungle.com 4y ago

Sorry, but you're already living in the “Squid Game”

one2three4
45pts105
medium.com 4y ago

Golang Sucks

one2three4
3pts3
theprint.in 5y ago

Pfizer and Moderna vaccines likely to produce long-lasting immunity, study finds

one2three4
6pts0
www.infoq.com 5y ago

The World Is on Fire and So Is Your Website

one2three4
2pts0
www.youtube.com 5y ago

China's Accelerating Bid for Chip Supremacy

one2three4
2pts0
www.atlasobscura.com 5y ago

When the Soviet Union Paid Pepsi in Warships

one2three4
2pts0
jessitron.com 5y ago

Those pesky pull request reviews

one2three4
2pts1
spectrum.ieee.org 5y ago

Programming Without Code: The Rise of No-Code Software Development

one2three4
3pts0
www.bofaml.com 5y ago

Robo Sapiens: Future of Work Primer [Bank of America Report 2021] [pdf]

one2three4
2pts0
www.newyorker.com 5y ago

How to Be a Stoic (2016)

one2three4
115pts64
lamport.azurewebsites.net 5y ago

TLA+ is a language for modeling concurrent and distributed programs and systems

one2three4
3pts0
www.dw.com 5y ago

AI arms race already underway

one2three4
1pts0
aninjusticemag.com 5y ago

We’re All Paying for Someone Else’s 4-Hour Work Week, Not Ours

one2three4
7pts1
doordash.engineering 5y ago

Migrating from Python to Kotlin for Our Back End Services

one2three4
2pts0
news.ycombinator.com 5y ago

Ask HN: How do you invent with such contracts?

one2three4
1pts4
www.theatlantic.com 5y ago

I’m Not Scared to Reenter Society. I’m Just Not Sure I Want To

one2three4
179pts292
vsupalov.com 5y ago

You Don't Need to Rebuild Your Development Docker Image on Every Code Change

one2three4
119pts62
news.ycombinator.com 5y ago

Ask HN: Was There a Hard AI It Would Maintain a HN Account. Wouldn't It?

one2three4
1pts4
www.pixelthoughts.co 5y ago

A 60-second meditation tool to help you clear your mind

one2three4
2pts0
www.dw.com 5y ago

Israel's Iron Dome proves successful against Gaza rockets

one2three4
4pts2
cabol.github.io 5y ago

Programming languages and multicore crisis (2013)

one2three4
2pts0
www.allaboutcircuits.com 5y ago

Cryptocurrency Mines Consume More Power Than Argentina–But PSUs Can Help

one2three4
7pts20
news.ycombinator.com 5y ago

Why porn industry comes with a stigma even in the technical world?

one2three4
8pts14
www.youtube.com 5y ago

Technology loses out in companies, countries and continents

one2three4
1pts0
futurism.com 5y ago

Japan's Plan To Dump Radioactive Water into the Ocean

one2three4
2pts0
www.businessinsider.com 5y ago

The purpose of Russia's 100-megaton underwater nuclear doomsday device

one2three4
6pts0
theloadstar.com 5y ago

Carriers eye savings by giving Suez a miss and going the long way round

one2three4
3pts0
arxiv.org 5y ago

On the Impact of Programming Languages on Code Quality

one2three4
2pts0
medium.com 5y ago

Should You Speak Truth to Power?

one2three4
1pts0
gcaptain.com 5y ago

Owner and Insurers of Ever Given Face Millions in Claims

one2three4
3pts0
Golang Sucks 5 years ago

Honestly the only real argument I've heard for Golang is that it is "coming from Google so it must be good". Every time I've tried to write in this language it feels like I'm hitting my head with a hammer.

Google might have very smart and knowledgeable people in it but this language is like a bad overhyped C. See next code that all it is doing is parsing a CSV line:

func NewPoint(line string) *Point {

tokens := strings.Split(line, ",")

if len(tokens) != 4 {

  return nil

 }

 var err error

 p := new(Point)
 
// why cannot I declare and assign err in one go??

p.id_ride, err = strconv.Atoi(tokens[0])

if err != nil {

  return nil

 }

 p.lat, err = strconv.ParseFloat(tokens[1], 32)

 if err != nil {

  return nil

 }

 p.ts, err = strconv.ParseInt(tokens[2], 10, 64)

 if err != nil {

  return nil

 }

 return p
}

most of the code has nothing to do with its functionality - it's just error handling that is plain hideous to write and read. Not to mention all the clutter to just convert an integer and a float.

And let's just not go into deeper aspects such as the structs that double as classes and has everyone creating his own style of SOLID and DPs. Or the inconsistent syntax which sometimes looks like traditional OO and othertimes like plain C further confusing users.

I find it very hard to believe that this language would have caught on if it weren't for Google pushing for it so aggressively. And I find it so disheartening to realise that after all these years developer productivity and happiness is merely an afterthought for language designers and that marketing and hype are the main drivers.

And yes I know the saying "there are languages people complain about and languages that people do not use". I find it worthy of high school gotcha sayings to which I reply that language designers of the majority of programming languages have no clue about how to make a language nice to its users. It's as they know how to design a internal combustion engine and then they put a chair and 4 wheels on it and they dismiss complaints about how unreasonably difficult and miserable the driver experience is.

I'm curious. Was Linkedin always so bad at securing its (our) data or things have gone downhill ever since the acquisition?

It is becoming a regular thing, almost part of the news cycle. "In other news, yesterday was the biannual data leak from Linkedin".

It is outrageous.

To keep your identity small is probably akin to becoming a small Buddha.

Identity is even a dominant political trend in itself. "Identity politics".

I agree with the premise of the post. I just cannot see how it can be done. I think it's better to learn to accept differences gracefully rather than minimizing the identity surface. It's also my way to test people and communities. Try to disagree on something they consider basic. They way they'll treat you shows who they really are.

I think it's similar to all the super-liberal OS licenses that permit any usage of OS SW without warranting any kind of compensation for the original devs. Licenses that the devs themselves are putting in their OS SW. Why they do so I honestly don't know.

Which leads to a number of weird situations like maintainers begging for compensation from simple users while behemoths make tons of money out of their SW or pretty basic SW being undermaintained (I vaguely remember a case pertaining to a security related library a few years ago where everyone was waiting on an overwhelmed and unpaid maintainer to provide a security fix).

Dunno. Some things just don't make sense to me. FWIW as far as my projects go I license under GPL. If it's free for you let it be free for all. I'd hate to be in the shoes of Redis contributors. To me, if your work is being used you must be compensated. Anything else is just plain wrong.

> Pynguin can cause serious harm to your computer, for example, wipe your entire hard disk! We recommend running Pynguin in an isolated environment, for example, a Docker container, to minimise the risk of damaging your system.

That sounds ominous.

Why do they execute the generated tests though? I mean I'd expect this to go only as far as generating the tests. Also that means that at least someone needs to review the tests.

OK. I WFH as well. I know all the benefits. And as I'm WFH for pandemic only I've been trying to find remote work post-pandemic and there I realized some bitter points:

1. I compete for positions with people all over the world. Who can complete with a fraction of the salary I need.

2. As a remote worker -most often working as a contractor- I'm even easier to be replaced in a heartbeat. No severance or anything alike.

3. Did I mention that I compete with all the planet? That makes competition for good roles really crazy.

4. Work blends into life and it is very hard to keep it from. This gets worse depending on the company/role but in general these things tend to go the employers way not yours.

5. You need to find new ways to socialize (and the motivation to do so is minimal) or you risk mental health issues.

All I'm trying to say is be careful what you wish for because you might get it.

Sorry for your loss.

Lost my brother-in-law few months back after a long battle with cancer. My sister is still mourning. It takes time and it never really goes away fully. You just get used to it I guess.

One of the things I thought and shared with her, and which had some effect was this: we all die and we all spend our time here in various ways. Being sad for a loss means that we were lucky enough to have someone of high value in our lives. That is not a given. So, sad as we might be it's also a reason to be happy that we were that lucky. The alternative would be to never have met them and thus lead a much poorer life.

Dunno if that helps.