Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sylware
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
121.
▲
by
sylware
3mo ago
Do you know of coding inference models I can access with curl? (namely with public access tokens, probably severely rate limited). Or some coding inference models I can access with a noscript/basic HTML browser? (namely basic HTML form
122.
▲
by
sylware
3mo ago
Zero usage of LLM (assembly coding, and sometimes plain and simple C). I cannot access them to test if they would be of any help in my coding use cases. You tell me once we get some inference access with a web API with public tokens (probab
123.
▲
by
sylware
3mo ago
Yep, I guess we are many to see what's happening with RISC-V. The most risk of cruft accumutation is in RVA... which is pursuing some level x86-64/ARM hardware compatibility. That said intel APX/AVX10.2 is RISC-V for x86-64..
124.
▲
by
sylware
3mo ago
Everything pushing forward RISC-V is a good thing (this time I get it right...) I code RISC-V assembly almost everyday, beyond the major point that it is a NON-IP-LOCKED ISA (unlike arm and x86-64), it feels like it does 'sweet spot&#x
125.
▲
by
sylware
3mo ago
It is not, the 'static' part is just some sugar to remove a bit more information from the internet traffic generated by such communication protocol. The software development part is mostly to mitigate what's well know with cu
126.
▲
by
sylware
3mo ago
The "less worse scenario of internet communication privacy" is direct IPv6(coze IPv4 with custom port redirections is messy, local custom IPv6 built on ISP provided prefix is much less messy) with custom UDP(or TCP, since its usag
127.
▲
by
sylware
3mo ago
But on the overall, based of the documents and information provided here, and what I think I managed to understand about them: it is not surprising some want to start the deprecation of C from RVA (some would even start its deprecation from
128.
▲
by
sylware
3mo ago
This is another way to say they are scared ofe competition and want to scrap them.
129.
▲
by
sylware
3mo ago
I thought so. But I want that :)
130.
▲
by
sylware
3mo ago
Huh? There are RISC-V "performant" implementations on the best TSMC silicon process like x86-64 and aarch64?
131.
▲
by
sylware
3mo ago
Many here wish for the non IP-locked RISC-V to get performant micro-achitectures for embedded/server/desktop/mobile that on the latest silicon process (without that, you can have a very good micro-architecture, that won'
132.
▲
by
sylware
3mo ago
Well, I said that because based on the documents provided here, it seems there are key people considering its removal even from the specs. From my point of view, just do like all the others: clearly deprecate it, namely say that "from
133.
▲
by
sylware
3mo ago
Thx for the github.com link, I can have a look at it.
134.
▲
by
sylware
3mo ago
mitigations do slow all CPUs, even those without the vulns. You need alternative linux kernels with their modules.
135.
▲
by
sylware
3mo ago
Maybe the best approach is to remove C from RVA while keeping it around in the specs for niche applications where text size _really_ matters (with current silicon processes, I wonder how weird those niche applications have to be to require
136.
▲
by
sylware
3mo ago
Cannot access the web site: whatwg cartel web engine only. Is antjs coded in plain and simple C?
137.
▲
by
sylware
3mo ago
You have to recompile the kernel to remove some mitigations about "indirect branching", namely you must have alternative windows kernels. Do you have those windows kernels?
138.
▲
by
sylware
3mo ago
English is not my native language and I wrote a bit too fast the message: I wanted to say that "everything pushing forward RISC-V is good". I code RISC-V assembly, I don't use C machine instructions (I don't even use the
139.
▲
by
sylware
3mo ago
"Free Software" is not enough anymore. We need _LEAN_ free software, including the SDK, then also the syntaxes of the used computer languages.
140.
▲
by
sylware
3mo ago
Everything RISC-V is good (even the mistakes which is making it more robust and more mature).
141.
▲
by
sylware
3mo ago
Don't forget to disable all "spectre and friends" mitigations in your linux kernel, and some workloads will become much faster. Can you do the same on the windows kernel or apple kernels?
142.
▲
by
sylware
3mo ago
Because it feels being pushed as hard as go programming language was in its prime time by gogol. It feels similar. For instance, the guy who pushed rust into the linux kernel was from microsoft, and those "microsoft is pushing rust
143.
▲
by
sylware
3mo ago
This page is blocked by a captcha not working with noscript/basic HTML browsers.
144.
▲
by
sylware
3mo ago
Please gogol, stop being super evil, restore interop with noscript/basic HTML web engines.
145.
▲
by
sylware
3mo ago
You can also write using sound based/compressed 'text message' dialect: unless a real human is reading, automated watching tool should have a hard time (until coded/ML-ed on such dialects I guess)
146.
▲
by
sylware
3mo ago
Are you misunderstanding on purpose? This is not specific to 'backdooring aes-gcm implementations' at all. Read again what I wrote, namely this is the general status quo on 'information system security': they don't
147.
▲
by
sylware
3mo ago
Who are the key people in control of the rust-lang repo? (besides microsoft obsviously) From which companies are they from?
148.
▲
by
sylware
3mo ago
And your REALLY think E2E is going to "protect" you? If the "services" want to watch, don't worry they will, "they don't need your password". But I guess they "do" that only for the very b
149.
▲
by
sylware
3mo ago
Since microsoft bought it, a whatwg cartel agenda was setup: slowly, step by step, noscript/basic HTML interop has been broken. Pure evil, microsoft, what else?
150.
▲
by
sylware
3mo ago
Is this true that microsoft rust syntax is now as worse than c++ brain damaged one?
More ›