HackerTrans
トップ新着トレンドコメント過去質問紹介求人

LikesPwsh

no profile record

コメント

LikesPwsh
·21 日前·議論
In the infamous words of Spolsky - "It’s harder to read code than to write it."
LikesPwsh
·先月·議論
Brexit harming the growth of both UK and EU is another perfectly valid interpretation of those numbers.

I'm sure there's a little truth to both, and noise from all kinds of other factors.
LikesPwsh
·2 か月前·議論
Rather than telling the LLM "loop through these files", tell it "write a script to loop through these files", then hard-code that script somewhere.
LikesPwsh
·4 か月前·議論
The same people who abbreviate "generative" AI in a way that misleadingly conflates it with "general" AI.

Fraud is just the default lifestyle of marketers.
LikesPwsh
·5 か月前·議論
YouTube on Firefox is a much better experience than the official YouTube app, so you can drop one from the list.
LikesPwsh
·6 か月前·議論
.net, dynamics, power, 365, azure, fabric, copilot.

There's always some pointless name change going on.
LikesPwsh
·6 か月前·議論
"IBM for i" is up there
LikesPwsh
·6 か月前·議論
Making up a bigger fraction doesn't mean that transaction fees will increase over time.

For L1 fees to actually increase over time, we need increased L1 throughput. Without that, increased demand for transactions causes more batching of transactions (mostly between exchanges).

Given the failure of BCH for pseudo-religious reasons I don't have much hope.
LikesPwsh
·7 か月前·議論
Skiddies targeting an individual site are a drop in the ocean compared with the industrial scale LLM scraping, so blaming them for it is in bad taste.
LikesPwsh
·7 か月前·議論
Most token holders use exchanges, where freezing accounts and just keeping the tokens is a daily occurrence.

That's not something solved by cryptocurrency in its current form.
LikesPwsh
·7 か月前·議論
That's infamously known as the "Oracle Problem".

Blockchain can't handle external state.

Smart contracts abstract it a bit by having a trusted third party or an automated pricing mechanism, but both are fragile.
LikesPwsh
·7 か月前·議論
The stated purpose of RTO may be more-nimble-whatever.

In practice it makes more sense if you always assume the intended purpose is to thinly veil constructive dismissal.
LikesPwsh
·8 か月前·議論
The original release came with separate Allied/Soviet discs. You could put one in your buddy's computer.

Keygen was also easily available.
LikesPwsh
·8 か月前·議論
Forge is a good modern equivalent
LikesPwsh
·8 か月前·議論
https://learn.microsoft.com/en-us/sql/relational-databases/s...

This one is a classic for MSSQL, most of it is applicable on postgres.
LikesPwsh
·9 か月前·議論
"Dimension table" is the name for lookup tables in a star or snowflake schema.
LikesPwsh
·9 か月前·議論
Some well known docs on the topic- https://use-the-index-luke.com/sql/where-clause/obfuscation
LikesPwsh
·9 か月前·議論
Yes
LikesPwsh
·9 か月前·議論
Anyone can generate an NFT, including IP you don't own or existing collections.

Hundreds of wallets might contain a the same monkey picture (or same hash and IPFS link to nitpick).

What matters is that Opensea says you have the "real" one.

Their database is the real list of who owns what, the blockchain is a distraction.

You can see it in their anti-theft systems. NFTs get hidden and blocked from trading after a police report, even if it's still there on the chain.
LikesPwsh
·9 か月前·議論
To clarify, I don't see users ever leaving centralised exchanges.

That means classic claims like "bitcoin is scarce" or "transactions don't require anyone's permission" or "transactions can't be censored" or "nobody can seize your bitcoin" are generally false in practice.

Even if a person only trades via bags of cash in dark alleyways and never touches exchanges, they're affected by all this "paper" bitcoin.

If they need to touch an exchange at any point, even if holding in a cold wallet 99% of the time, that exchange can still take 100% of their tokens.