138 karma · joined April 18, 2025
> Android Gea apps packaged as a native Android APK, rendered through a WebView
Why webview? No love for android?
This is on iOS 13.6
I have no idea why tailwind needs or does something which makes it utterly unusable. I miss the days when many websites used to offer simple html versions of their apps, like gmail (https://techcrunch.com/2024/02/22/google-is-killing-gmails-b...)
[1] - https://www.statista.com/statistics/1118859/mobile-apple-ios...
This seems poorly worded or genuinely concerning. Why do you want to track my email, username or anything in my profile. What do you do with it? How do you track it?
Which parents and which developers? How many of them? From where?
In go, if I don’t know a constructs definition, i know exactly where to look at and find it.
When exploring a new language I won’t always setup an ide first. I just want to look at the documentation on my own. Heck, any language which requires ide or any mandatory tooling to work with it, is already handicapping a developer.
G# seems to copy go syntax but didn’t copy the things that go makes it easier to understand any go code.
It can get bit tedious as one progresses, you need to push yourself to continue. Not sure what can be done to motivate yourself to continue. But I did enjoy since it didn’t make me restart if I lose a round.
Is the work predefined,ie, how much will each person do?
> Some have the group leader as the first name, or the 'big shot' is always first. My impression is that in medicine it is often a kind of ranking from 'most to least' main author
Does this affect your standing in workplace or industry? When we read about papers in scientific journals, news, or even arxiv, they mostly refer to the work based on first name, like “potato-peeler et al”. Sure it’s for brevity But when you look at the authors, there maybe 10 ppl listed. I have always wondered how do they get recognised. Since Like you mentioned they have to contribute. If they contribute but their names get swallowed up within “et al”, how does someone know how much was their contribution?
Any suitable examples? In the linked posts it gives querying weather service as an example but still uses a cache. Even with a normal concurrent request to a single function, a caching layer can be added before it makes any external request. Or am I misunderstanding this use case?
Study software engineering. Or study in general. Might improve your comprehension issues.
You can’t provide me any technical answer.
But nevertheless , if any language provides something like that, win-win for entire ecosystem.
I am unable to understand your point or you seem to be making arguments that have nothing to do with the article nor with my earlier replies. I wonder why. Are you expecting sundar pichai to announce golang to his shareholders in his quarterly call? Which language does that?
This article and my replies are technical in nature. You need to have a technical response to a technical problem. You cant get emotional everytime. Which language allows me fast builds, lightweight and high performance concurrency, strong stdlib and tooling, easy cross compilation with static binaries, simple syntax, decent performance and by that i mean not worrying too much on memory management, easy onboarding and large scale maintainability? I am willing to try that tool.
This obsession with one liners is inversely proportional to professional experience.
The article is on point on the strengths of go, and in many cases, those other languages you say, you will find it really hard to do the same thing with the ease with which you can do in go.
What the article glosses over, is the footguns with working with the language. No compile time nil checks, implicit interfaces, lack of sum types, like you said, which more so often leads to bloated structs, member visibility which is just private and public. You can find more.
But these problems were not the main focus of go. Go was build because google devs wanted a simpler way to manage and deploy their software across thousands of services, not having to wait forever for their code to compile, not worrying about writing cpp code in the BEST possible industry standard, ability to do parallel processing of hundreds or thousands of workloads without choking your cpu, managing dependency hell. These were actual roadblocks. And google was not the only one facing these problems. Go solved all of it. Which language was solving this before go?
Wrong thing to be bothered with. This allows static analysis of every possible path the code can take. Try to do that with throw/catch. There is a reason many industry guidelines like misra, jsf, etc just outright ban hidden paths. They have been literally catastrophic. There is a reason why many modern languages like go, rust, etc, want errors to be explicitly handled.
Go documentation specifically reasons why they treat errors-as-values and why is it like that - https://go.dev/doc/faq#exceptions
> Rust converts the common case boilerplate down into one character: ? which lets you focus on any exceptional error handling rather than a wall of if statements that almost all look alike
Again, wrong way to look at errors. Errors are not a problem for a compiler to resolve. Errors are part of your business logic. They need to be explicit and handled. The syntax of one language vs another is not the point of error handling. Errors are not a distraction. It is your job to review each path the code can take.
Code may be written once, but code is always reviewed or audited or referenced more than once. No one is impressed if you write some meta magic one-liner. I would rather be more impressed if I can read your code and form a mental image on how many paths your code takes to achieve an outcome in a single sitting, instead of pinging you for a quick call to explain yourself.
> you go blind looking at them all and can't spot the difference
> And these days people probably just type "tab" and their LLM assistant fills out the entire block incorrectly in one keypress copying the pattern from everything else
Now, if someone is 'going blind' looking at error checks, its because their function is doing too much and has too many failure points. Perhaps one may need to focus on honing their software engineering skills on how to structure their code, instead of hitting that 'tab' more so often.