yuchi

Even better, you can just use a single listener and on click verify the element under the cursor with document.elementFromPoint

The actual size may change a lot depending on the font, but there’s a nice Unicode symbol for that:

——— <redacted> ———

Update: apparently HN doesn’t like some characters…

Anyway these are the characters: https://unicode.org/charts/nameslist/n_2700.html

- 2700 Black Safety Scissors

- 2701 Upper Blade Scissors

- 2702 Black Scissors

- 2703 Lower Blade Scissors

- 2704 White Scissors

Another interesting fact is the difference in quality of the armours exchanged. One was incredibly valuable (gold or bronze if I’m not mistaken) and the other one was relatively poor.

Xenia was such a powerful social norm that for a warrior, in the heat of battle, is perfectly fine to temporarily be nude, exchange your finest armour for a lower grade one, and still be happy about it.

The solution from literature is “use color as much as you want (within the limits of sufficient contrast for readability) but nether rely exclusively on it, always add some other visual device, such as icons or (even better) textual additions”.

Marko predates scelte, by at least 3 years

Short form:

1. Focus on advantages and benefits of your product straight on.

2. Do show your product. It’s hard and difficult to keep it up to date, but the value outweighs the cost.

3. Use short memorable phrasing, but expand as necessary.

4. If your product has nerd value baked into it (e.g. some powerful protocol that mainstream competitors do not implement) do make it a major feature but explain the benefits to the uninitiated (“we support JMAP, the more powerful alternative to IMAP that allows you to use X app and service”)

5. On the visual side: keep it simple and add a single gimmick, such a background pattern or a strange gradient. Reuse that same gimmick in subtler versions with color/shape/position variations. Always strive for readability, not effect.

6. Pricing must be easily accessible. Explain in simple words if exceptions apply (student discounts etc)

Sorry to sound stupid and probably out of topic, but at the end of the article the author placed a (I infer) satirical image of what appears to be doubly linked gravity wells, a typical wormhole by Hollywood explanations. At the top the author placed “This is not a wormhole”.

Is this a reference to “this is not a pipe” (related to the description ≠ experiment argument of the article) or they actually mean that that rendition does not represent a wormhole?

Actually that’s the italian voice

They interrupted the initiative for revenue loss.

Now I want a “This ‘x does not exist’ does not exist”

Personally built similar but incomplete solutions in my projects way more times that I’d like to admit.

Could you elaborate on your roadmap on CRDT / real time collaboration? If it’s in plan and will be executed correctly I’m completely sold.

Anyway, congrats, looks awesome.

UPDATE n. 2: Dylan Field (CEO of Figma) has addressed these kind of concerns on their public disclore of the fact: https://www.figma.com/blog/a-new-collaboration-with-adobe/

Citing him:

> Adobe is deeply committed to keeping Figma operating autonomously and I will continue to serve as CEO, reporting to David Wadhwani.

As others have said, there’s really a missing OSS version out there that can compete feature-by-feature with Sketch / Figma / XD. Layout engine capabilities are the biggest missing feature in competitors.

If true, congratulations for Figma founders, and a bad day for designers that were looking for a way to escape from Adobe.

I don’t think that in the long term this will give Figma as an ecosystem any benefit — unless Adobe will keep it separate from the main Creative Cloud.

This reminds me of the Trello acquisition.

As a loyal Figma user I’m pretty sceptical of the future. Hope to be wrong.

UPDATE: Looks like it is indeed true… https://news.adobe.com/news/news-details/2022/Adobe-to-Acqui...

This argument is very similar to what I usually, probably inappropriately, refer to “malleability” of a software, interface or system in general: it’s ability to be used way beyond the initial use cases, and hopefully be good at it.

/Getting/Ferrin/

Been there just last weekend. It is an amazing experience. For an engineer mind is an incredible masterpiece. Getting (the creator) is always there supervising the maintenance of its creations.

They are a little bit hard to operate but the feeling of enjoying a ride that has been propelled by your own legs is terrific.

I cannot suggest enough to pay the place a visit. Also do absolutely eat there, the price is right and the quality is incredibly high for the type of food.

Please fix the title. GitLab is capitalized with both G and L as upper case.

Since those are percentages it could simply mean that a great amount of Java positions opened up in that period, stealing percent points from other categories. This explains the symmetry, but not the causes.

May it be a huge amount of positions have been incorrectly labeled for Java instead of JavaScript (you know… Ham / Hamster) and then corrected a month later?

That’s correct for Sciter, but Tauri uses the OS’ browser engine, so you’re back to the hostile environment / unknown territory of the web.

A 3d dimension version would require wrapping… I wonder if such a shape exists! (I don’t want to spoil this micro challenge more than I already did)

This approach is over-engineered to say the least…

You can implement such a layout without using Grid Layout and using just Flex Layout. Also with some min-/max-width tricks you can also completely avoid having media queries in there…

For beginners in HTML/CSS this approach is absolutely distracting IMHO.

Some more details. They are using Highlight.js, and `attribute` is what is applied to (S)CSS properties too. But both `left` and `right` are valid properties. What I think is that `\r` is treated as the special Carriage Return character and therefore doesn’t allow `right` to be identified.

The reason is that their blog rendering auto-identifies that code block as SCSS and treats “left” as an attribute. Which is strange, since I cannot find something for “left” that is not defined for “right”.

For example, I cannot find a “left” attribute here: https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes

Thanks for your effort. Having a piece of my childhood made open source makes me so happy.

Very sad to discover that this is NOT a ready made component to display actual trees. What a deceitful name!

Jokes apart, nice library. Will try it out sooner or later. May I suggest to not use children as the prop to Ps the Node component? Maybe a more explicit NodeComponent prop would have been better imho.

Point is, Deno is doing a lot to bring feature parity with expected Web APIs (which are not part of JavaScript the language yet), and they are building a single export standard library, but padStart is not part of their (direct) actions.

Sorry but padStart/padEnd are part of EcmaScript 2019 (or near that year). Deno did not implement it. (AFAIK)

The reason behind this different naming convention comes from the diversity in experiences of the original team. This will/did prefix instead of “on” comes from Mac OS X/iOS patterns and allows the name to convey the “when” of the listener. It is not “during component mounting” it is “after it did”.

I think it’s the wrong term completely. This is old school deobfuscation.

This is the first time I wrote his pseudonym… I never saw it is not Disasterpiece but DisasterPEACE…

THANK YOU for letting me know