neurotrace

If you're using `apply`, you might as well have just written the CSS normally, imo

Components don't stop the soup though. It's a fundamental issue where you're just replacing inline styles with classes. But hey, you do you

I have _serious_ doubts about the longevity of tailwind. It adds unnecessary tooling to recreate inline styles with theme support. I tried adding it to a project which used other technologies listed here and it was obnoxious to use. You end up with class name soup unless you combine all of the styles under a combined class. Once you do that, it's literally just normal CSS with extra steps

I agree. I haven't read the original so I can't speak to the accuracy but it's a pretty good bit of sci-fi that I look forward to every week. I get the feeling that a lot of people have a lot of emotional attachment to the original and it's upsetting that it doesn't live up to their expectations. However, that doesn't mean that it isn't good.

Starship has been my daily driver for something like a year now. It's been lovely

I can't be bothered to type all of it out on my phone but even adding in those pieces, it doesn't change it much. This is F# so you can easily manage the async via an async computation expression, the retry logic can be encapsulated in the `sendEmails` function, and the error handling is reduced to a `Result` which is very easy to work with in a pipeline. Not everything should be done in a pipeline but pipelines make a lot of things a lot nicer

I didn't think I had to make this clear but a lot of people seem to be getting stuck on the specifics of my example code. That example is doing nothing but showing a 5,000 foot view of what pipelines can do. Please don't take my dumb example that was written early in the morning as The One True Way of processing data, sending emails, or handling errors. It's a horrible example of that

The example I gave was contrived. I frequently find myself modeling much of my logic as a series of data transformations. The more I can model logic like this, the easier it is to test.

For what it's worth, your example doesn't map 1-to-1 to the intention of what I wrote. Doing it in a more imperative style, I'd have to write

    emails = list()
    for user in users:
        emails.push(user.email)
    res = sendEmail emails
    if res.IsError:
        Error("Error sending emails")
    else:
        res

(excuse my pseudo Python)

This is a huge one for me. I jot down random notes as I go. Some are very descriptive and detailed. Others are as simple as "things of this shape seem to have this property." Just getting it written down seems to help solidify things more quickly. I rarely re-read these notes.

Seconded. I've been using Foam for some time now and it's been great. Since it's all VS Code, it's also very hackable

Oh perfect. Thanks! Great work on the project by the way

What made you decide to build it from scratch? By following a different system you're leaving a lot of free work on the table. For example, I extensively use Vimium, Dark Reader, Stylus, TamperMonkey, and LastPass. By doing it from scratch, all of those extensions would need to be re-implemented in the SigmaOS API. I love the idea of SigmaOS but I can't abandon Chrome/Firefox if I can't have LastPass, for example.

Are you planning to adopt an existing browser extension API or will extensions need to be rebuilt for Sigma?

Death isn't the only thing that comes from the virus. You're also ignoring all of the younger people who are immunocompromised or otherwise susceptible to the effects of the disease. Alternative suggestion: everyone just get their shots just like they do their flu shot and we can all move forward with our lives.

Depending on the country, you may be able to work remotely while on a tourist visa. This is true, for example, in Mexico. The tourist visa allows you to stay in the country for up to six months and you aren't allowed to work for a Mexican company but they have no issues with you working for a company in another country.

I used Thunderbird for a very long time but recently stopped. Every update has made it slower, breaks a host of extensions, and the Google Calendar integration is consistently broken no matter which solution I use. I really, really want to use Thunderbird but email and calendar need to Just Work. I can't keep fixing it every time they push out an update

I'm on mobile so forgive me for not giving more extensive code examples. In my case, I'm building my app with React, TypeScript, and react-jss. I've got an enum which stores my common media queries and I just use it in the style declaration.

    button: {
      [MediaQueries.Medium]: ... 
    }

I can't use CSS variables for that but I personally don't think it's useful to let the user redefine those queries anyway

This makes me so happy. My group of friends migrated to Guilded a while ago specifically because threads are so useful. However, Guilded is too janky to recommend on it's own merits. I'm so stoked to return to Discord

Let me just preface this by saying that I'm not anti-crypto. From what little I know about it, it's an interesting tech. I just literally don't understand _why_ people use it. So I dug in to what you mentioned.

Layer 2 Rollups

> Layer 2 is a collective term for solutions designed to help scale your application by handling transactions off the Ethereum mainnet (layer 1), while taking advantage of the robust decentralized security model of mainnet. Transaction speed suffers when the network is busy which can make the user experience poor for certain types of dapps. And as the network gets busier, gas prices increase as transaction senders aim to outbid each other. This can make using Ethereum very expensive.

So it makes Ethereum cheaper. As someone who doesn't really get the hype, this doesn't help at all. Making Ethereum cheaper doesn't help me if I don't have a reason to use Ethereum.

After Googling "ethereum proof-of-staking migration" my take away is that moving to proof-of-stake will make it more robust and more energy efficient. Again, it doesn't tell me anything about why I should use Ethereum (or any other cryptocurrency) in the first place.

Everything I read about crypto talks about how it's currency that can be produced by anyone* and blockchain inherently makes it possible to know who did what and when. As a layperson, none of this is interesting or useful. The average person isn't going to start mining, the average person isn't going to speculate on a very volatile market, and the average person has no way to spend any crypto that they own. I'm not saying it's your job to fix the optics here but I've read a ton of comments in this thread and not a single person has pointed to something that made me think "I could use that" and I'm the kind of person who likes to browse Github looking for weird things to try out.

* Provided you have enough money to build a powerful PC and afford the electricity cost

I'm not OP but this doesn't seem to answer the question. You presented a lot of speculation and mentioned two things that I've never heard of

Someone may say that "he" is gender-neutral but it's not in practice

For anyone interested in seeing a side-by-side comparison: https://viewsync.net/watch?v=uX0Ye7qhRd4&t=4&v=hcareEsIXHM&t...

On memorizing: for me, it hasn't been difficult. Specialty layer switches are placed on keys that are difficult to press so I don't accidentally hit them. Additionally, since they're out of the way, it's easy to remember them because of the difficulty.

For more common layer switches, I extensively use dual-use keys. For example, if I tap "F" then I get the letter "f" but if I hold it, it switches to a vim-like layer. HJKL becomes arrow keys, Y becomes Ctrl+C, etc. The point is that you don't have to dedicate more keys to do layer switching. You can have the same key do different things depending on how it's used.

For me, memorizing has been easy due to incremental change. I didn't come up with my new layout on day one then stick to it forever. I'd find a frequent pain point, tweak the layout, and memorize the tweak. It's easy to remember 2 or 3 key changes at a time.

> Long story short, this is the single reason why I haven't bought an ErgoDox/keyboardio/… so far.

I don't really understand this conclusion. The point of these programmable keyboards is you can make them as work-free as you need. If you hit your function keys all the time, you can make the number row produce a function key just by holding it for a little longer or do like what OP did and make number chords match a function key. Press 1+2 to get F1, 2+3 to get F2, etc.

I understand not wanting to use a layer for everything which is why I don't care for ultra minimalist boards like the T-34 or Plank but an Ergodox has plenty of keys for my uses.

Yes

It's a cool idea but I wrote a userstyle to override it. Reading on a plain color is easier for me

I use it in production. Some of the choices they made grind my gears (I'm looking at you ordered `open`s and poor inference for records with similar shapes) but overall it's pretty nice

Personally, I like having my dev environment and my note-taking environment be the same. I finely tune VS Code to do what I want and I miss those features when I'm editing elsewhere. If I setup configuration or plugin that's non-optimal for note-taking, I can adjust that in the workspace settings

Foam doesn't take a very prescriptivist approach. A flat directory is the path of least resistance but you can put things in to separate directories. Personally, I store all of my daily notes in a separate folder and everything else in the root

There's a plugin for that https://marketplace.visualstudio.com/items?itemName=mushan.v...