HN user
As someone diagnosed recently, I can confirm this. People think it is a linear set of symptoms/traits, and not a bouquet of clues. Disclaimer: I previously was one of those people, and I typically dont give a rats ass on what people think :)
Im developing something vaguely in the same space (tamper proof audit log) - (or several things since I also have a custom temporal object mapper for postgres); what is the advantage of this project? It doesnt seem sql-compliant (afaik bitemporal operations are part of the SQL-2011 standard), and what this could add -tamper detection - seems absent. Not criticizing, just trying to understand the use case.
Me. You know nuclei is written in go? Sometimes you need resolution consistency between eg. A port scanner and nuclei. You build and test this on your infra, but then you need to deploy on a heavily proxied network and you find issues. Is this your fault? Yes. Because you use golang. (Note: I use golang for almost everything, and this is something it is not documented enough - I am aware of this and have been bitten in the ass by this more than once)
None. There are no good actors in a profit-driven endeavour. But open-weight seems pretty good (the chinese)
Reiserfs. A good example on how oss cannot save the product. There are others, but this is the first one that comes to my mind. If you use clearly unethical oss, are you just using oss or are you a part of the problem? Typically, oss purists take these into account.
Some fun trivia: https://en.wikipedia.org/wiki/Ea-n%C4%81%E1%B9%A3ir
Good question. No. Since the press was invented, our records have improved tremendously, partially because of the low cost of maintaing them. However, we still have detailed records from many eras, tracing back at least 3000 years. The egyptians had archeologists, let that sink in.
You can take note. Writing is a physical action, e.g. performing output.
Writing is an action. You can memorize, take a mental note, but you are not writing.
(Someone else mentioned Camōes, a portuguese who famously/allegedly saved his writings from a shipwreck by swimming with one arm and using the other to keep the book above water; your interpretation of "writing" is an insult)
If you are a 250 year old nation built on "stolen land" (by the europeans, mind you), I would assume not many. But the US has been home to many great writers. This is just stupid.
To be clear, there are excellent american authors, and many comments mention them; its more of a "why am I reading stupid questions about history?"
Reducing these countries to a single name is probably the reason why we can guess this was written by an american; each country has at least a bunch of inspired authors per couple of generations. The country it is actively being bombed right now is the "modern" reincarnation of a nation that is roughly 10x older than the US. We all know who american Homer is, and this is the first year ever we whish we was the president. Friggin noobs.
One of the projects Im working on and off is a tamper-proof audit log, based on some PoC code I created almost 10 years go; unit and integration testing are good at preventing defects and regressions, but they will not guarantee your software will work. However, with the power of LLMs, one can easily use model checking (in my case with Quint) and/or other formal proof approaches to ensure the software conforms as specified. The result (in my opinion) is an implementation guided by a single human that is actually more trustworthy than manual human-made software using the traditional approach.
Disclaimer: im not an expert on this. But serious implementations outright mention jepsen usage. Just saying.
This article is about Cloudflare developing for their own internal control plane--I'm fairly certain their requirements preclude a single Postgres.
True, but the article claims both strong consistency (sort of) and linearizability; that is basically a serializable writer and a lock; if I read correctly (I haven't read all the details), the article conflates both; afaik it is possible to have linearizability with eventual consistency; algorithms to solve concurrent writes and having multiple writers in raft is a "solved problem". sad to see such a spotty article on such important topic by a major company, even if the underlying paper is strong. This feels like manure.
I had no idea mandriva/openmandriva still existed. I still have a mandrake cd somewhere, mostly because I cannot seem to be able to depart from physical media :)
Lol. Honestly, I love Munich, but I totally understand why certain movements galvanized there :p its easy to be on a high horse on a rich land - if something is not right, must be someone else's fault.
One of the reasons is that Germany is not a friendly country for non-german speakers (and/or if you dont have the right profile); I've worked for a while in both Berlin and Munich. In berlin you get away with english, except anything official - from opening a bank account to any interaction with the city council or government services. They will go out of your way to make you feel unwelcome if you are not a fluent german speaker. In Munich is even worse - in many "non-immigrant neighbourhoods" they wont even acknowledge you if you speak english (eg. In the supermarket), though often they understand it perfectly.
Learning german is not easy, but it is absolutely essential if you want to call it home; Id suggest anyone planning a move to start learning beforehand - the idea that you will "wing it by talking to people" is not enough.
This is - by far - the most stupid stuff I've read on the internet the past few days. They didnt find cancer either (as well as a plethora of diseases that could be related to the symptoms), and afaik its not in the report.
Yah you can argue that the tool is not ideal for that diagnostic, yadda yadda. I get it, and in the end I agree with the subtle difference you highlight, because it is something that makes sense to a certain kind of people. You know how many medics would read the report exactly like the author did? Too many.
How do I know? Im not in a wheelchair after being constantly misdiagnosed by using the wrong imagiology technique by (mostly) chance, and a good help from friends, including a surgeon. This seems to be a case where AI would be a valuable doctor tool for differential diagnosis; instead we have know-it-alls that can't bother to verify, and AI that often gets details wrong. That is the problem.
Yes, they did. And the motivation is quite simple: money.
Having the US control export your flagship model is the ultimate stamp approval in the AI race. All headliners are american, but one us too poweful to be made available. It just reads like if someone was riding an IPO.
It is also, paradoxically, a wink to the 90's. But we're not in the 90's, and the cat is out of the box, and in 6-12 months everyone else will be at this tier. This is, clearly, an attempt to boost a model that isnt that revolutionary. I used Fable, and for my work, its mostly a waste of tokens. It seems a bit better than Opus 4.8 - but 4.8 the past week(s) has actually been top knotch; so lets make it a "myth" and have secops tell stories about it, so everyone will pay when the time comes; will you, ceo/cto, allow your company to fall behind? Of course not. You will pay. For modest results, apparently, but the hype is there.
10 years ago, I was headlining a project where we had strict performance requirements (ssr, php mind you) - the target for any operation except login was 30ms, and any endpoint taking more than 60ms in one of the devs server would have to have explicit approval. Add the nework RTT if you dont want to have a local backend, and for most geographies is still well under 300ms. Fun fact, we actually designed a system that could be easily replicated between regions and/or perform internal routing, leveraging the operator network. 3 AWS regions would make the RTT of a request well within <100ms on average for >80% of the world population. Requests were mostly "instant" - the big trick that did it (at the time) as to avoid reflow in the browser. Funny how the spotlight is now on doing stuff that "solves" that problem with the technology that was designed to solve that problem.
Corner case: actually, it can. Also, thats how auto-updating works ; depending on local state as a source of truth using browser apis is a terrible idea IMO.
The whole concept of "assume it is committed while we sync in the background" is, in the most cases, a terrible architectural decision, unless it is coupled with explicit feedback (eg. A small visual indicator indicating if the background queue is empty or syncing). Also, it breaks temporality: last-update-wins no longer holds, because update time and sync time are decoupled. And you also create a new problem, which is local cache coherence.
It may be a good fit for some systems (though I cannot think of a single one), but in general is just a horrible solution.
Openevidence.com is not available in the EU, so I would actually be weary of recommending it. You either be exposing personal info, or getting a result you cannot guarantee it hasnt been tainted/canned to sell you something.
Why not just ask for context and approval of the legal team? That would generate enough trail so some shady requirements get dropped almost immediately; having your superior explicitly sign off in writing a feature you deemed unethical and/or potentially illegal is a great way of actually removing them from the pipeline. You can even frame it as "a good guy" just alerting him/her that there may be a fallback, so make sure it has all necessary elements. Compliance decisions are often above a developers paygrade, and one should squarely document the culprit on any shady decision - and boy, this is very easy in big organizations where no single decision-maker wants to be accountable.
Yes, something like "analyze throroughly the @datasheet.pdf and create a plan to implement x"
They are - probably more proficient than with some high-level languages. I've used it for embedded stuff, including TI sitara PRU assembly, with great results. Frontier models can also easily "learn" directly from the manuals; asm is quite easy for them to pick up due to its "flat" (non-structured) nature.
Funny how windows updates are never postponed for lack of "scaling". I know, I know, completely different stuff here - but arent test vms and ci vms being updated constantly?
Im old enough to remember the hotmail migration to win2k (then 2k3) and the postmortem. I was also old enough to look at the rotor source code. Yah, that one, running managed code in freebsd.
Im still waiting for... Basically anyone that has used TFS (what microsoft had/pushed before acquiring github) to do a similar post, detailing how they miss the tool original concept. I'm sitting down, don't worry about me.
We all understand that. We had some piece of software we still cling on to it (in my case is a copy of paint shop pro 5, corel draw 7 and Delphi 7), despite being completely obsoleted or assassinated by "big industry". I could add CoolEdit 2000 to it, but havent really opened it in a decade.
To be honest, I never understood the fascination with github. Its a hub, of git repos. Not to piss on your parade, because your complaints are valid, but maybe isnt github that as gone sour as much as you have grown out of it. This was your passion, now its over and you move on.
Wide tables and rich data. Dozens to hundreds of columns, some of them a json dimension. Way easier to explore these datasets with AI
How is this different from "people that cant write sql should not use orms"? With code agents you can write raw sql better than most developers; and if you want, you can basically ask for the same implementation using whatever orm you want. Lastly, AI generated code is supposed to be reviewed by a human, just like code done by your colleague. Thing is, with AI, you can establish automatic review guidelines, and even ask for proper benchmarks and optimizations, at zero cost.