HN user

tumetab1

570 karma
Posts3
Comments275
View on HN

Also they are anti EU and NATO. Lot of astroturfing here.

At the same time, that big advertising and crony politicians are fighting to impose digital ID for all internet communications... one of the strongest privacy advocates is being attacked with non-sense.

Expect EFF to be bought or attacked.

The only valid argument against HTTP GET with a body is that it has privacy/security risks.

Exist stuff (caches, CDN, etc.) could serve private information because the HTTP GET is cached without checking the request contents. The new standard can avoid this because old stuff does not know about HTTP QUERY.

Likely caused by better performance provided by IPv4.

Browsers try both stacks (Happy Eyeballs algorithm) so likely the IPv4 is working better for your visitors.

Since must people use IPv4 most of the time, IPv6 performance issues go unnoticed by the users, ISPs, CDNs, etc.

I follow Go security issues and many recent ones are consequences of features added to Go and also security researches following up on an area after one issue is found.

Recent examples are certification validation logic, one issue after an another... because it's a mess of thing to implement.

I agree with your comment, but I disagree a both the example opinions... complex is the discussion :D

I heard something that helps better framing those discussions, use "familiar" instead of "simple".

An highly abstract way to access a database table, with ORM for example, can be simple because everyone is expecting it and knows how to do all tasks (changing schema, troubleshooting, managing transactions, etc.).

Doing userService.pgSql("select ....") in the same way can be simple.

True.

By chance, recently in an architecture discussion document I added that one of aspects to consider is how easy is to remove (the whole thing) if it's not wanted anymore.

It was an obvious case because it was an AI capability, which can be become deprecated/useless/too-risky very fast.

Since you're getting into a senior role, learn the mantra, it depends :D

The usual trade-off of a well paid software development job is lack of job security and always learning - the skill set is always changing in contrast with other jobs.

My suggestion, stop chase trends and start to hear from mature software developers to get better perspective on what's best to invest on.

And why the mantra is always true?

You can find stable job (slow moving company) doing basic software development and just learn something new every 4 years and then change companies.

Or never change company and be the default expert, because everyone else is changing jobs, get job security, work less hours and have time within your job to uplift your skills.

Keep chasing latest high paid jobs/trends by sacrificing off time.

What's the best option for you? Only you know, it's depends on your own goals.

For those paying attention, NGOs supported by the EU are good example.

Here's a news link https://www.euronews.com/my-europe/2025/01/23/use-of-eu-fund...

I don't have time/will to find more consolidating information but some EU-Elites regularly use NGOs to support their own policy goals, against member states governments and their populations. They always excuse themselves by saying they fund everyone... but one side of the issue usually gets more funds than the other.

If I recall correctly in one "EU wants to monitor the internet" regulations, EU directly funded targeted AD campaigns to convinced some Member state populations to support it so the government would change its intended vote. They were caught and backed off. Then they funded some NGO to do it :D

I appreciate that "tools" that are used to build the final version of a module/cli/service are explicitly managed through go.mod.

I really dislike that now I'm going to have two problems, managing other tools installed through a makefile, e.g. lint, and managing tools "installed" through go.mod, e.g. mocks generators, stringify, etc.

I feel like this is not a net negative on the ecosystem again. Each release Golang team adds thing to manage and makes it harder to interact with other codebases. In this case, each company will have to decide if they want to use "go tool" and when to use it. Each time I clone an open source repo I'm going to have to check how they manage their tools.

My personal estimation is that this will be noticeable in the first six months of 2025 in the USA big tech organizations.

I think this is actually already in motion in board meetings, I'm pretty sure executives are discussing something like "if we spend Z$ on AI tools, can we avoid hiring how many engineers?"

I was intrigued by the value so did some research.

I would guess the 15$/hour value was chosen to approximate an average gross salary. The annualized payment would be 31200$[1] and it seems the average annual salary was around 30359$.

Updated to 2022 values the annual gross pay would be 10033€ [3], current average annual gross salary is 20483€ [4].

[1] 15$ * 2080 hours [2] https://www.repository.utl.pt/bitstream/10400.5/9819/1/ee-ja... [3] https://www.ine.pt/xportal/xmain?xpid=INE&xpgid=ipc&xlang=en [4] https://www.pordata.pt/pt/estatisticas/salarios-e-pensoes/sa...

Zero upside, probably a downside.

Apple has a top notch logistics and security processes which had mitigated the issue of supply chain attack in China which his willing and capable of producing such attacks.

Moving some production to the USA might induce some sloppiness in this due a perceived inferior risk.

Also, some security measures requested by Apple to manufacturers in other countries are probably illegal in the USA.

The reason multiplayer servers implicitly trust clients is because it's a cheaper and proven (less risk) solution.

The traditional anti-cheat can be just slapped after the game is developed in most games. If the game is very successful then you can just update the game with extra paid protections provided by the anti-cheat tool.

The alternative is local game engine that works with a partial game state which is a challenge on it self. If you still can make it work, you will still have to deal with people "modding" the client to gain an advantage. E.g.: enemies are painted red instead of camouflage.

Google Pixel 9 Pro 2 years ago

hummm, found the "read message" language setting... I doubt it it will work properly but will try

Thanks :)

Google Pixel 9 Pro 2 years ago

If you're unlucky enough to be bilingual, it's a complet joke.

Yep, it's just pain :D I'm native portuguese speaker but I navigate the english web.

Hey siri, read notifications (portuguese name bad written) sent message <random portuguese read as english>.

or:

E aí siri, lê notificações (read notifications in portuguese) Notificação de Twitter, <english post read as portuguese>

2. Arbitrary precision numeric data types with vetted operations and rounding modes.

Be aware that a good rationale for choosing the database but you should enforce a specific precision per table otherwise you can get nasty accounting bugs because you're adding a 3.0095 amount with an 9.99 amount.