Hacker Newsnew | past | comments | ask | show | jobs | submit | Squonk42's commentslogin


Thank you for finding this! Depili does great work! In another comment I mentioned that I've been working on the Casio CZ-101, which uses the NEC μPD7810 processor. Depili created a processor spec for the μCOM-87 architecture, which I've continued working on in this PR: https://github.com/NationalSecurityAgency/ghidra/pull/7930



Hilariously lots of "logging" (lucene based) tools explicitly require storing JSON docs and fall over if the schema's not quite right[1].

I regularly deal with situations where devs "log" by sending "json" to stdout of their container runtime, then expect the downstream infrastructure to magic structure into it perfectly. "You understand something has to parse that stream of bytes you're sending to find all the matching quotes and curly braces and stuff, right? What happens if one process in the container's emitting a huge log event and something else in the container decides to report that it's doing some memory stuff?" <blank stare> "I expect you'd log the error and open an incident?"

(the correct answer is to just collect the garbage strings in json (ha) and give them unparsed crap for them to deal with themselves, but then "we're devs deving; we don't want to waste energy on operations toil"

Later people ask "why's logging so expensive?"

Sigh.

[1] opensearch / elasticsearch, obvs

[2] https://12factor.net/logs


Why are semicolons mandatory? Wouldn't be cleaner without this restriction, like in Kotlin?


A valid question! Semicolons and other forms of syntactic redundancy often enable much better error messages. We're leaning towards keeping them in Vale.

However, we can always change our minds later and make them optional, so it seems wise to just require them for now and revisit later.


Given the possible confusion with Vale[1] and Vala[2], I suggest to rename the language to some new unambiguous name asap in order get more visibility.

Otherwise, it looks very promising!

[1] https://github.com/project-everest/vale [2] https://en.m.wikipedia.org/wiki/Vala_(programming_language)


Github may show a warning when creating repo about all possible name collisions. We see this problem often. If anybody from GH is listening :)


GitHub already has a feature to check if any public GH repo has this name. They've called it search.


I don't think this is really a problem. I know Vala and I don't see a problem with confusing the two.


It's because you know Vala that you don't see the problem.


I didn't confuse it with Vala, but with Val:

https://github.com/val-lang/val


This is not the first Arduino board that is not OH, I first complained about the Arduino Yùn 6 years ago: https://squonk42.wordpress.com/2015/02/22/arduino-yun-what-i...


And LicheePi Zero, LicheePi Nano...


It is possible to build a CPU without a single gate: http://www.inf.fu-berlin.de/inst/ag-ki/rojas_home/documents/...


The CPU actually contains many gates, only the ALU is a single gate.


That uses a NAND gate in a similar fashion as the MyNOR


No, look at the conclusion, there is no more gate for the ALU.


"Device Warranty: 30 Days" => Totally illegal in my country


Across the whole of the EU this isn't legal (the legal minimum warranty period is 2 years[1]).

Legal aspects aside, it also isn't exactly a vote of confidence in the quality of the product. I mean, 30 days, really?

1: https://europa.eu/youreurope/business/dealing-with-customers...


It may be illegal to sell locally but completely legal to import for personal use (e.g. because Pine64 isn't conducting business in your country at all, they have no obligation to comply with local regulations, only you, the importer of record, have those obligations and you probably aren't required to provide yourself with a warranty).


(and in all of Europe I believe)


I think it may be legal, since saying it qualifies as a disclaimer. Basically the default is 24m (EU) or 12m (US), but it should be legal to explicitly state another term for warranty.

Some shops have down to 1 week of warranty, some (e.g. wholesale items) may state to accept no returns, etc.


> I think it may be legal, since saying it qualifies as a disclaimer. Basically the default is 24m (EU) or 12m (US), but it should be legal to explicitly state another term for warranty.

No. While in the US people seem to be able to get away with anything as long as there is a disclaimer, EU law is strict - it's minimum 24 months per Art. 17 EU directive 1999/44/EC (https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CEL...), with an exception for second-hand goods (Art. 16 of said directive, with the decision on the exact duration being left to the member states).

B2B transactions, however, are pretty much unregulated wild west.


Same here! I am forwarding this article to all my coworkers!

I am currently using the Allwinner V3s, and the review is covering this part accurately.



Which is undoubtedly why so many free CAD programs are hitting HN today.


Oof good thing I stayed away


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: