arp242 / arp242.net Goto Github PK

I just wanted to thank you for the information you took the time and effort to give at your site. Much appreciated and useful!

https://www.arp242.net/license.html is pretty convincing in switching from AGPL to EUPL, but

Bad: The GPL Compatability is good, but the way it’s worded less so; you can distribute “Derivative Works” as GPL in its entirety, rather than just the changes made. In other words, you can circumvent the stronger copyleft.

European Union Public License has ineffective network protection by default.

Have you managed to solve this problem?

The correct spelling is "Torvalds". Is the typo on purpose?

I would really like to hear your comparison between YAML, TOML and UCL.

Link: https://github.com/vstakhov/libucl

I was curious about the cleanup process, but the script is missing, and the GitHub repo search doesn't give me any useful results.

The last paragraph of “On being the right size” seems to be broken:

As [Haldane already observed many years ago][haldane], the “right” size isn’t the smallest (or the largest). It’s the right one.[testing]: /testing.html [fp-why]: https://stackoverflow.com/a/2835936/660921 [haldane]: https://irl.cs.ucla.edu/papers/right-size.html

I’m viewing the site on Safari running on iOS.

In https://arp242.net/weblog/yaml_probably_not_so_great_after_all.html

Don’t want to start the spaces vs. tabs debate here, but if tabs would be allowed I would be able to (temporarily) increase the tab width to a higher number to make it easier to see – this is sort if the point of tabs

Should be "of" instead of "if"

In your jquery.html article you don't mention zepto which is basically jquuery just without all the legacy browser support.

https://zeptojs.com/

The parsed version of the YAML should be
{13: 'Tilburg', 'Effenaar': 'Eindhoven'}

013 is a popular music Venue in Tilburg, but YAML will send you the wrong way:

{11: 'Tilburg', 'Effenaar': 'Eindhoven'}

https://raw.githubusercontent.com/Carpetsmoker/arp242.net/master/_posts/2016-09-04-yaml_probably_not_so_great_after_all.markdown

So about first example:

Pages like You might not need jQuery try to sell the idea that it’s easy to ditch jQuery, but the very first example is a good reason to use jQuery: one line of trivial jQuery code gets replaced with 10 lines of vanilla JS code!

that 10 lines example is only for IE10+,... IE today is totally dead, and we have fetch() that is as short as writting $.ajax(), well no, it's even one character shorter.

About selectors? You can create one/two line alias for $(), like https://stackoverflow.com/a/46079132

so I think, this whole article is one big bullshit.

Btw. today when we have things like Svelte, usage of something like jQuery should be totally illegal.

Or how would You do this in jQuery? https://svelte.dev/examples#numeric-inputs because in Svelte it's practically without writting any JavaScript at all (well except declaring variables, that is so trivial)... I'm sure You would need to write 20x more code in jQuery...

and even two years ago, it was already bullshit.. all my arguments are correct for 2019 too.

You might want to include a link to https://github.com/cblp/yaml-sucks somewhere near the bottom, referring to compatibility. Pretty nice list of variation across interpreters.

https://www.arp242.net/git-hg.html

because it became a problem, [as Greg Kroah-Hartman explains][linus-fanboys]:

I am guessing that it is markdown and one of that likely should be in ( ) - probably second, but not sure

I've stumbled across your post on EUPL: awesome! pretty much agree. Now there is only 1 bug on the website: it doesn't answer my curiosity about the arp242 nick;) is it about ARP'ing Front 242? if so, the correct ARP reply is of course: Aarschot, Belgium, EU

Hi, thanks for the interesting article. I didn't read it all, but once I stopped to question if I actually like reading YAML, my thoughts:

• I find it weird, coming from a C syntax background, it's a bit alien.
• I like coding in python, but counting white space is not what I want to spend time on.
• Despite being noisy, I'm used to curly brackets and semi-colons.

So I stumbled on your article when deciding on a config format for a big project I'm working on. It's heavily geared to FreeBSD where UCL is more considered. Some developers are trying to port the varying and inconsistent system config file formats to UCL, but that's about as easy as IPv6 adoption. UCl is inspired by the nginx config (I think).

Anyways, I decided to go with UCL. There's a nice shell command utility to work with UCL configs by the name of 'uclcmd'. It leverages the official libucl library (link below). One great thing about UCL (libucl) is that it exports to YAML and JSON and looks pretty solid and performant. I was trying to find out how good UCL was for serialization vs YAML.

Perhaps you could take a look at UCL and make an article of your impressions of it.

https://github.com/vstakhov/libucl

Reading this post https://arp242.net/weblog/browsers-conflict-interest.html and it's pretty good and I agree with it - except for the section on Do Not Track.

I don't understand the point being made by it. The screenshot you provide of their notification does not seem inaccurate or scaremongering or somehow negatively influential.

In reality nowadays very few entities honor DNT and it makes users more easily fingerprinted. That is to say, it makes it easier for the bad guys to track you. For those reasons I don't recommend it to people.

Hey there, I've stumbled across your site by reading an article mentioned in Javascript Weekly. I have to admit I like the minimalistic site Design but thought that topics like the one about jQuery could be more vivid including a comment section. Since you prefer GitHub issues as a feedback channel I wanted to make you aware of https://utteranc.es which essentially creates comments as issues in your repo. Take a look at my blog for a sample https://pragmatic-coder.net

Great articles, keep up the good work

the error handler proposed in the article is:

set_error_handler(function($errno, $errstr, $errfile, $errline) {
	throw new ErrorException('error');
});

• which completely ignores the error message and severity (ErrorException's constructor has a way to report severity but your code is not using it), and error_reporting flags, and also makes the @ error suppression operator useless. the error reporting flags should be honored, and i think you should use the example from http://php.net/manual/en/class.errorexception.php instead:

function exception_error_handler($severity, $message, $file, $line) {
    if (!(error_reporting() & $severity)) {
        // This error code is not included in error_reporting
        return;
    }
    throw new ErrorException($message, 0, $severity, $file, $line);
}

As if you need to a dick to people to maintain “quality”.

Should be:

As if you need to be a dick to people to maintain “quality”.

Also found this one, but it's less confusing:

Here’s another thing I’m complete fed up with: the “know-it-better”.

Should be:

Here’s another thing I’m completely fed up with: the “know-it-better”.

Hi, i just read your article about YAML files and find it awesome !

Can i translate to Brazilian Portuguese ?

Hello,

would be so kind to help me here?

Thanks a lot in advance!
Alex

It was a shitty comment, but he did correct it which is saying a lot in Stallman ters, as I haven’t seen him do that very often.

This should be terms, right?

Hi!

about https://arp242.net/weblog/yaml_probably_not_so_great_after_all.html :

I agree that yaml doesn't help you much with the problems of large structures in documents, and it's unfortunate that there are so many specs that require using large documents with too few considerations of modularity. The modularity part seems to be one aspect in which yaml can actually help a bit, trading screen space for the effort of remembering anchor names.

However, I'd rather consider display problems a concern that should be addressed by an editor. If I understand your argument for tabs correctly, it boils down to: "My editor can configure how wide tabs are displayed, but not how wide spaces at start of line are displayed, thus the document should be adapted to fit my editor's feature set." I know, it's really hard to find the perfect editor, unless you code your own. ;-) Same for a missing (or lazily implemented) fold and/or "split horizontally" feature that lets you divide the scrollbar into an arbitrary number of document parts, so you can keep table headers (or container names and their indentation) at a fixed position while scrolling the below part of the document.

How far will my suggestion "your editor should do that" dissuade you from considering those a YAML problem?

Might want to mention this:

https://github.com/pasztorpisti/json-cfg

I think it addresses the biggest problems with JSON as a config:

• comments
• trailing commas
• better syntax errors

... without adding a bunch of new syntax or complex features.

In his how I do my computing page he additionally writes that he uses the icecat browser with tor to connect to sites he doesn't use regularly.

I am aware the footnote regarding the matter is a joke, but it may or may not be worth adding this detail for context. I know rms can be incredibly strange, but there's no need to present him as sillier than he is.

Hey, I found your article on YAML interesting. I don't have much by way of a dog in the fight, though I do like YAML over TOML. Perhaps I'm just more familiar. On the whole, I found your article well thought out and reasonably balanced. But, I had a couple thoughts to offer:

First, you might like the video platforms have values, which I think applies here. I found the video from a talk on Rust where the author applied this to languages. My point is that each markup language would have its own set of values. Your challenges with YAML might be a value conflict. When you complained that YAML was too complex, it's value was "YAML is expressive and extensible." It is not that they did not reach this goal, but that you disagree with it. Which is perfectly fine. Some people love C# and Haskell...and Pepsi.

Second, you said the goal of YAML is to "YAML data is portable between programming languages." A markup language's aspirations cannot compel all the programming languages to adopt it or apply it properly. That is up to each language. It is unfair to penalize YAML for a third party's problem. Can we blame John Gruber for the various flavors of Markdown?

Anyway, good article. Thank you for making me think. Have a great day.

You mentioned a 17k jQuery build on your site that doesnt have sizzle?

Im just curious, is that something you build custom or how would you go about including that in a project?

I share your sentiments about Stack Overflow's egregiously poisonous tone. To which I'd like to comment that Stack Overflow is not as great as it thinks it is. Two problems I'll highlight:

• Aggressive closing of duplicates that are not exact duplicates.
• Obsolete answers.

These reinforce each other over time and have rotted S.O.'s answer set to the point of uselessness for many questions.

Between this and the toxic culture I am entirely deterred from participating and have neither the incentive, nor the clout, nor the inclination to help fix it. I participate in more welcoming, competent, and technology-specific forums instead.

Hi, great post!

Here I would like to point out one important benefit of tiny unit test code, and not just having Integration tests. When code is changed and unit test fails, the error is more close to the source code that caused the error.

In integration test, you need to spend more time to figure it out the cause.
As you stated, this creates duplicate testing code, but I think that the tradeoff is reasonable.

Very similar when you need to put input verification checks both on client and server side. It is duplicate check, but in order to satisfy security features, it is a must.

I like very much the idea of making blog comments as github issue.

Regards, Karlo.

The starting and closing tags are mismatched, first is Raining... and second is Rain...

In your article about signing emails in the paragraph about s/mime you wrote:
"The downside of this is that anyone can sign their emails with a valid key, which isn’t necessarily telling you much (just because haxx0r.ru has a certificate doesn’t mean it’s trustworthy)".
How is this difrerent from PGP? In PGP too everyone can have a valid key, in both systems the point is that they let you verify who owns the key/certificate, so if you receive a message claiming to be from Amazon but the PGP key or the certificate belongs to haxx0r.ru you know that it's a phishing attempt.

I like your article on "stupid light" and the analogy with hiking. On my website I like to say it a slightly different way: "Simplicity is not the opposite of complexity. Simplicity is too often an excuse for being simplistic. The world doesn't need any more stupid software. The opposite of complexity is beautiful, elegant design."

In other words the right amount of simplicity, but not too much. I like to say there is genius in simplicity, it takes hard work and requires careful design.

I read your article Easy means easy to debug and really inspired from it.
Thus I want to translate it into Korean and share your great article with my people.
Can I ask you for a permission? Thanks in advance.
Of course, I'll add reference to your original article on top and if you want, I'll let you know the link to translated article.

Para. beginning "I’m that sensitive or get offended easily, . . . " should be "I’m not that sensitive or get offended easily, . . . "?

Thanks, I wanted to know how good they were.
I wanted to use .json instead .ini