taink

This was cool, but the best thing was the dedicated transition guide from LaTeX to Typst[1].

The bottom section especially, which is a list of Typst's shortcomings compared to LaTeX. This helped a lot when actually choosing this over Overleaf for the last writing project I had.

[1] https://typst.app/docs/guides/guide-for-latex-users/

I don't know if this is a reputable source in any way but a quick search shows this: https://www2.mouser.com/c/?processor%20series=STM32H753

The only big thing missing for now is their OS (or rather, their Illumos distribution), Helios[1].

Can't wait to read its source code, I was curious since reading this thread[2].

[1] https://github.com/oxidecomputer/helios (if this is not found for you, we're in the same boat)

[2] https://news.ycombinator.com/item?id=33337086

Hello, well done on your article!

I have a few questions:

- What exactly do you mean by "Semantic CSS"? I've never heard this terminology before (might just be OOTL). I get the parallel between this and Semantic HTML, but I guess it's not as clear what it is supposed to mean for a styling language to me. Is it just native CSS (or "pure" CSS)? At least, as a result, I have no idea what this means, or by what measures you decided what constitutes "semantics" in Tailwind's CSS:

  The most surprising thing is that Tailwind uses more global/semantic CSS than the semantic approach itself ¯\_(ツ)_/¯

- A small nitpick, maybe: could you somehow replace the top links to the two versions you compare with actual HTML links instead of JS events? This prevents middle-clicking and the location is replaced so it's tough to compare the two sites while reading your article. I have to click on your link, copy the url, and open that in a new tab. At least, opening the page in a new tab would be nice.

I had to dig a little so here's the link to the talk the article is mentioning: https://youtu.be/L98v4epQmrg?t=15121

The article you linked to doesn't explain plainly how the cataloging system works. Going to Wikipedia[1] makes it a little more intelligible, but honestly it still sounds pretty complicated.

If a cataloging system is difficult to explain in plain and simple terms, it will be tough to advocate for it with other people. I might put in the effort but how can I quickly convince others to do so?

Johnny Decimal is pretty simple in comparison, it's 4 bullet points:

- A JD number is two numbers with a dot in between: XX.YY

- First digit of first number: a broad category

- Second digit of first number: a sub-category

- The second number is incremented each time you create a new folder (which you want to be careful about!)

Once you've explained that and you show a basic folder structure, people will understand how it's used, at least. That's where it performs better than your system.

It's probably fine if it's tough to define, but it has to be simple to teach.

[1] https://en.wikipedia.org/wiki/Library_of_Congress_Classifica...

> It’s developed in Estonia! Estonia has a remarkable IT and software culture (I live there) and every so often you come across an absolute gem. This looks like one of them

What sets Estonia's IT and software culture apart from other countries? What other Estonian software would you recommend?

You should update your docs because this is not what they say. I seem to understand you just started the open beta -- congratulations. You should still mention your product is in beta on your homepage (or at the very least, your download page).

EDIT: How can I see which nodes are in the network? There's only one ID on https://networks.any.coop/ and I don't know what to do with it.

That's useless if the client also sends the same data to Any's node. You can't disable that for now:

  Self-hosting only without a backup node is currently unavailable

  The self-hosting-only feature is not released yet. If you don’t want to use Anytype node and instead use p2p sync between your devices, you can block Anytype network traffic (Anytype & Anytype Helper) via your firewall.

From https://doc.anytype.io/d/data-and-security/data-storage-and-...

They seem to have only one "node" so far, because the software is still in alpha? That's what their docs seem to say[1].

  All your data primarily syncs to the encrypted backup node in the current alpha. For alpha testers, the application is always connected to the backup node and cannot be disconnected.

Their homepage could tell this more clearly. It doesn't look like it's in alpha.

[1] https://doc.anytype.io/d/troubleshooting/self-host-your-back...

While I understand why a font's website would behave this way, I don't think making people dowload 1598 (!) lines of fonts[1] is a good idea; it honestly took so long I was wondering what was so special about their font right about when it started to kick in.

[1] https://input.djr.com/css/fonts.css

There should be a picture of what you are supposed to see on the article[1]. It works on this page for me but some of the other articles do not show it. Seems weird because I'm not changing browsers in between.

[1] https://images.ctfassets.net/f20lfrunubsq/2FuQMHycwersLjIf4d...

Weirdly enough I can't see it on this article but it's showing just fine on the OP. Maybe my extensions?

I think they were planning to support the first generation fairly long-term, so you probably don't want to wait for a Steam Deck 2.

I think I've seen people that can't get their hands on it through "official" means get their own by arranging a delivery through someone else on Reddit for instance. I don't know if you'd be comfortable with that solution though.

EDIT: they are planning to support the Steam Deck long-term, but they said nothing about the first generation -- my bad[1].

[1]: https://cdn.cloudflare.steamstatic.com/steamdeck/images/pres...

I wouldn't go as far as saying CommonJS is hurting JavaScript, but it's current status in the node ecosystem is definitely painful. I mean the default remains CommonJS, so using esmodules is awkward on 'native' node, but if you use the most popular bundling systems, the default becomes esmodules. I won't pretend I know which is better between the two, but the decision should be made to either make it optional or deprecate it if esmodules is really the Best Module System™. The current in-between is far from ideal, that's for sure.

I haven't used Gitless before but usually these types of abstractions fall short for me. It never helped me as much as truly learning git.

I learned so much about the commands that intimidated me by playing "Oh My Git!"[1]. It's an open source game that presents commands as quick-to-understand concepts and lets you experiment with them by using playing cards on the visual rendition of a repository. I was honestly surprised nobody else mentioned it here, maybe it's not that well known.

Of course it's not completely accurate all the time in its descriptions but it sure helps understanding the underlying workings a bit more, and it pushed me into actually reading the manual.

[1] https://ohmygit.org/

I agree that a "Sonic Hedgehog" gene would sound silly but honestly I don't see how "BEBOP" qualifies as silly. What would be the better alternative? Cultural references are a good way to name things. A style of jazz is not a bad choice.

Additionally:

  The newfound world is called BEBOP-1c, after the name of the project that collected the data, BEBOP, which stands for Binaries Escorted By Orbiting Planets. (BEBOP-1 is another name for the binary system TOI-1338.)

Keep in mind there is no complete feature parity with NPM. This only allows you to use packages not present in Deno's ecosystem, but it does not guarantee it will work flawlessly (and in practice it can be a pain to use some packages).

The best way to use Deno and take advantage of its benefits is to use Deno's packages. Allowing NPM packages is a good strategic move because on top of already being quite different from Node, there are not many packages, but it does not take away from how well it will work with Deno-native packages.

Don't forget your basic organization sabotage field manual: https://archive.org/details/SimpleSabotageFieldManualStrateg...

I agree that copyleft is more about "giving forward", and I think it's a confusion a lot of people make. Reading through the thread, I get the impression that some think as soon as one "distributes" the licensed material, original authors should get a copy. I'm extrapolating of course, but even then I feel some people would agree with that statement.

GPL, for instance, merely states that distributed sources or patches "based on" the program should be "conveyed" under the same terms. In other words, anyone who gets their hands on it will do so under the same license.

If anything, I would be worried that GitHub trained itself on publicly-available but not clearly licensed code, because then it would have no license to "use" it in any way[0]. GPL provides such a right, so there is no problem there. It would be even more worrying if the not clearly licensed code was in a private repository but I think I remember reading that private repositories were not included in the training data.

However, would you consider a black box program, of which the output can consistently produce verbatim or at the very least slightly modified copies of code from GPL code to be transformative? The problem does not lie in how the code is distributed but in how transformative the distributed code is. Not only does the same apply to any program besides AI-powered software, it applies to humans[1].

Given how unpredictable the output of an AI is, one should not be able to train itself on GPL code if it cannot reliably guarantee it will not produce infringing code.

[0]: https://docs.github.com/en/site-policy/github-terms/github-t... (https://archive.ph/susi0#4-license-grant-to-us)

[1]: One such example would be how Microsoft employees allegedly prevented themselves from reading refterm source code, cf. https://github.com/microsoft/terminal/issues/10462#issuecomm...

Assuming what you say here is true (which in my opinion is a pretty high leap), one could then ask why those biases exist in the first place. I expect authoritarian states to enable corruption but it's the contrary in the case of Singapore. Why? Because I doubt it boils down to the salary of the ministers.

On a side note, it might be interesting to see the evolution of this index over the years for any given country; that might lead to interesting conclusions on the bias confirmation you're talking about!

This is the best authoritative source that I could find. The few assertions I've seen that Singapore is less corrupt than most european and north american countries quote Transparency International as a source, so I assume it might be an acceptable one. They also supplement their findings with a "GCB" survey[1] (which is less recent), and given enough time I guess there are other sources one could find.

These are surveys, so there's a limit to how reliable their results can be. However, I find surveys are a pretty good start when you need to get a general idea on how something does and you can't just measure it. How you value that is up to you, that's why I quote it in my comment.

[1] https://www.transparency.org/en/gcb

Singapore remains an authoritarian state, not a democracy. It allowed for massive progress in a difficult political climate but it does so at the cost of a good amount of political freedoms. That might be fine, but not in all cultures.

I also challenge the notion that higher pay leads to less corruption. If so, then why are Denmark, Finland, New Zealand and Norway ranked higher in the corruption perception index[1], when they are paid much, much less annually (especially Finland)[2]?

[1] https://www.transparency.org/en/cpi/2022 (https://archive.ph/fabjP)

[2] https://en.wikipedia.org/wiki/List_of_salaries_of_heads_of_s... (https://archive.ph/XGbpO)

No need to trust it -- that's the best part.

I tend to trust blogs or conversations with other people more than I should. The benefit of a tool like ChatGPT is that I already distrust it, and I tend to double-check more often what it responds.

I agree with you, but the comparison and fine-tuning GP mentioned are really areas where it's an unparalleled tool right now. Dismissing it in fear of "contaminating your understanding" is missing out on what the tool may offer to you. It's not really that much worse than a search query.

> Also, I'm not sure if it even treated individual digits as separate tokens, but it might. Someone with API access can check.

Anyone can check, they have a tool for that[1]. It's mentioned in their FAQ article[2].

According to their tool, GPT-3 counts the following as one token:

- any combination of or below 3 digits

- 1111, 3333, 6666, 9999 (it tends to group other digits in groups of 2)

- 66666666 (so 8 sixes -- 5, 6 or 7 won't work)

- 00000000 (anything below 8 zeros counts as one token as well, probably to handle millions and billions)

- 0000000000000000 (16 zeros)

This isn't an exhaustive list, there are probably a lot of other weird edge cases I haven't tried. Its failure to understand basic arithmetic makes much more sense given how inconsistent the tokenizing of digits is done.

[1]: https://platform.openai.com/tokenizer

[2]: https://help.openai.com/en/articles/4936856-what-are-tokens-...

To be fair in practice I can't think of a good methodology to automate this selection.

This is probably something that would be determined much later, on a case-by-case basis... which is ideally solved by manually curating such knowledge. You lose some in the process but I'd argue something "critical" should bring attention to the necessity of its archiving.

This comes pretty darn close to what the author is asking!

> Right now every channel is meant to be both transient and permanent. I know that’ll never change, so create a new “Lore” or “Archive” channel where the moderators tap on wisdom and preserve-forever statements or threads, and they get added over there. Think of it as “Pinning” but they’re pinned forever and there’s a bunch of them.

Disc.wiki seems to literally provide a similar feature, check!

> Make it possible to export this Lore/Archive channel to a reasonable file, like JSON or any other text format.

Disc.wiki provides a web interface for browsing "pinned" messages. HTML is a mostly parse-able text format, so check!

> At the very least, consider some sort of “FAQ” feature/contingency that does a similar function to the old-style FAQs, so people can contribute sets of knowledge in a structured manual instead of an endless search for terms from everyone who ever touched a server.

Ok, there's still some room for improvement. Disc.wiki's homepage claims their docs[0] are built on disc.wiki, so something similar could work.

There could be an open source version of both the cms and the bot but that's at least a step in the right direction.

[0]: https://disc.wiki/docs

The flaw isn't that it is not realistic enough, but that it goes too much against an average human's preconception of how a basic traffic system should work.

It is absolutely not unreasonable to expect a 1993 game to not choose a random route at a junction; it should use a basic pathfinding algorithm (which were well-known, even in 1993) to choose the closest one.

Of course it is limited by performance but optimization is hardly a good counter-point to intuition in this kind of game.

Perhaps a better question would be how can we wear our wearable wares so that they don't wear out from us excessively wearing them?

Would it ruin my health? Most of what I've read suggests otherwise, do you have any suggestions on further reading about this?

And I'd expect any fabric to wear out when you wear it (there's probably a good pun to make here).