Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
za3faran
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
26 ms
·
481.
▲
by
za3faran
3y ago
As a Middle Easterner, we reject that notion.
482.
▲
by
za3faran
3y ago
> We inherited a world where for many generations, men were hostile to women. It was unfair and needed rectifying. Perhaps in an American/European centric view of the world. I would heavily challenge/reject that assumption acro
483.
▲
by
za3faran
3y ago
It's different when your company deals works in a life critical space.
484.
▲
by
za3faran
3y ago
Many lives and resources were also involved in the rescue operation.
485.
▲
OceanGate Website Unreachable
(oceangate.com)
4 points
by
za3faran
3y ago
|
3 comments
486.
▲
by
za3faran
3y ago
Having worked on several large golang code bases, those issues popped up all the time. Yes we used the errors package, but as with the rest of the language, you end up having to reinvent the wheel poorly and in an error prone manner. Incide
487.
▲
by
za3faran
3y ago
When I had to learn golang, picking up the syntax was easy, but it has many gotchas that you end up having to spend time to learn them anyway, which don't exist in Java (e.g. the Java compiler requires final or effectively final vars t
488.
▲
by
za3faran
3y ago
You can add context to a stack trace. So it's strictly a super set. And seeing the code path taken to the error is anything but irrelevant.
489.
▲
by
za3faran
3y ago
Which proves that there is more load on the programmer to ensure that no two error messages are the same. What is this, are we back to programming in C with __LINE__ macros?
490.
▲
by
za3faran
3y ago
You can see the path that was taken to get to those 20 levels. Without stack traces, you're left to manually peruse the code base to figure all those out.
491.
▲
by
za3faran
3y ago
We all know that documentation always 100% matches the behavior of the code :-)
492.
▲
by
za3faran
3y ago
It sounds you're conflating an older framework with Java the language.
493.
▲
by
za3faran
3y ago
This is why you can do const true = false in golang The number of reserved keywords is not a bad thing. For example, I constantly missed `final` when I worked in golang. Just because a keyword doesn't exist does not make its usecase di
494.
▲
by
za3faran
3y ago
I'm strongly convinced that the google brand name gave it a big push. Its predecessor (Limbo if I recall correctly) went nowhere. It did bring uncolored async to the mainstream, but as in typical golang fashion, it was very verbose and
495.
▲
by
za3faran
3y ago
Could you elaborate on exactly what complexity in Java you're referring to? By having an overly simplistic language, you end up pushing more complexity onto the programmer and into the code base. There is no free lunch. I find it much
496.
▲
by
za3faran
3y ago
Yet, the bulk of code written at Google remains Java and C++. golang's approach to uncolored async was decent, yet in the same manner of the language, overly verbose and error prone. Passing channels everywhere gets tricky quickly, and
497.
▲
by
za3faran
3y ago
Nothing you wrote is specific to golang's error handling though, and in actuality, ends up being more brittle because it is possible to miss handling such errors. At least an exception would bubble up instead of keeping the program run
498.
▲
by
za3faran
3y ago
Nothing is preventing the code from returning both at the same time. I've seen code (including in the standard library) that returns both an error and a return value. In a language with disjoint unions, such cases would be encoded prop
499.
▲
by
za3faran
3y ago
You basically end up reinventing stack traces, with all the possible ways context can be missed. This summarizes the language quite well.
500.
▲
by
za3faran
3y ago
I also worked on a very large golang codebase, and error traces were sorely missed. Searching for the error string is not sufficient. What happens when the string changes in the master branch, which is different from the deployed version? W
501.
▲
by
za3faran
3y ago
How does it address it? By making it painstakingly verbose (not to mention error prone) to deal with errors? Not referring to you personally, but I've heard that sentiment several times now, and I have not seen anything to back it up (
502.
▲
by
za3faran
3y ago
The provided examples highlight exactly why error handling in golang is verbose, error prone, and lacks context. Do people really not care about stack traces?
503.
▲
by
za3faran
3y ago
How much of a performance hit were they causing?
504.
▲
by
za3faran
3y ago
I've seen the same in golang, which ironically is supposed to be vehemently against OOP.
505.
▲
by
za3faran
3y ago
> but still we have noticed how it is affecting and changing how she feels about the world around and herself. Are you able to elaborate on what you noticed? > The girl gets complaints from her parents because she reads too much books
506.
▲
by
za3faran
3y ago
Patterns of socialization meaning what exactly?
507.
▲
by
za3faran
3y ago
Computers pre-social media were different. You could do a lot offline. Today, social media has been proven to be extremely toxic. There was a paper submitted to HN that mentions how much worse mental health is the earlier a child gets a cel
508.
▲
Design document on nullability and value types (Brian Goetz)
(gist.github.com)
4 points
by
za3faran
3y ago
|
1 comments
509.
▲
by
za3faran
3y ago
The Abrahamic religions are not western.
510.
▲
by
za3faran
3y ago
Not quite: * https://openjdk.org/jeps/417 * https://youtu.be/1JeoNr6-pZw
More ›