noxecanexx

Nothing against gitlab as I use and pushed for it in my company, but I feel it's heading towards Azure Devops(this might be entirely baseless). By that I mean it's geared more towards enterprise teams and business than startups looking to build stuff and deploy. I say this off the complexity of their UI, their feature set and what they seem to prioritize.

+1 for this. I use it with notion(and pinned tabs) so I can have multiple workspaces with multiple emails

You're not alone. No matter how much I hate chrome, I've never been more displeased by an app as I am with Firefox's mobile app. We might see a new one though based off firefox preview so hopefully I can make the complete switch soon

I actually went ahead to learn haskell after one of his recent talks(my motivation was the vehement rejection from the haskell community..on reddit mostly) I haven't turned back since then. It's either he doesn't really understand how types are used or he's intentionally "bad-mouthing" types(which I don't think he's doing)

I would assume most android users think android is cheap rather than free. It would be interesting though to see their response to such price hike(if it ever happens)

That's the thing. The EU is not trying to tell Google how to make money from android. It's only saying it can't force installation of search and chrome. It's upto Google to find another means of making money that won't exploit their dominance in other markets

I think it should still be possible to seperate view from the service at the backend, even if that means defining more routes. I am talking from the hiccup(clj) point of view though

You can do the same with server rendered apps. I don't think reacted and co invented components

+1 for the last paragraph. I used that technique to quell my desire to use event sourcing everywhere

I was with you till the 32Gb memory part. In what part of the world do users have devices with 32Gb RAM(barring gamers)

> Nowhere have I said that if you see an error message you don't know how to program.

> making it approachable and stooping to the lowest common denominator.

> We agree errors are useful even if we disagree that Clojure's errors are bad.

I would assume that you disagree with the article then, in which case I can't make any other point to emphasize that

As a clojure programmer myself, it surprises me to see other clojure programmers say this. Error messages are an important part of programming and that you didn't face many errors doesn't mean others won't and doesn't mean they don't know how to program either. Even the article above clearly states that error messages are bad.

This is very true. The same way one doesn't know if a background was started is the same way you can't know if a file was written to or some global state was changed. I thought async/await solves most of his examples

You are falling into the same trap described by @chiefalchemsit. Saying normal people should have common sense only makes matters worse

I second this. Programmong languages where made to be precise enough for computers to understand and ambigous enough for general computing

Came here for the same reason. Although I am more interested in what @rauchg is doing

Exactly. Proposing that businesses change their attitude towards liability when there's no clear downside is just self deceit

@jVinc's post answers this. They didn't state specifically that he was warned six seconds before the crash.

But that's the thing..the 5Gb data is mostly made of stuff you "uploaded" to Google, not stuff that was "collected"

It's been almost a week of this. Actually wondering when we'll get back to interesting tech

The funny thing is I actually faced this problem a lot last year. Since I read paul grahams essay on hackers I decided to focus that will for hard problems into my side projects(although this has taken my focus from popular frameworks to specialized libraries)

when you say simplicity is objective it means there's only one definition. I would really like to know what that definition is plus where to find such exauhstive list of qualities of simple code.

Honest question. What's wrong with using a calendar widget for DoB.(engineer here)

One thing I am yet to see is a critical analysis of over-engineering. I constantly see articles like this that talk about how those young developers are looking for the newest and shiniest technology and I think that's just a lazy answer to the causes of over engineering. I for instance have tried my best to run away specifically from the new shiniest things like Kafka, webpack, mongo. But this is obviously a flawed strategy as those technogolies my help solve my problems. One might say careful cost/benefit analysis is the answer but it's most times easy for me to point out how much more beneficial the tech I am introducing is. And it could be but it would still be over engineering. Plus it's not really solving the real problem that is adding more incidental complexity to the solution than needed. It would interesting to see an article on causes of over-engineering from real examples so one could extract potential solutions.

At least tic-tac-toe isn't designed to suck all your attention

Exactly, most especially after seeing this comment https://news.ycombinator.com/item?id=16087079

Thanks a lot for this

Thanks. I might start with simplifying my dev workflow, the perhaps some appliances