skysight-inc/HackerNews huggingface dataset:
I wrote a 10-line script to interactively query JSON documents using jq from vim in a tmux pane. Like jid[1], but better. Here it is:

jq-repl () {
local query_file json_file new_pane_height nodemon_cmd change_aucmd jq_args
query_file=$(mktemp)
json_file=${query_file}.json
cat /dev/stdin > $json_file
new_pane_height=5
jq_args="$@ -C -f $query_file $json_file"
nodemon_cmd="clear; jq $jq_args | less"
change_aucmd="au TextChanged,TextChangedI <buffer> write"
tmux split-window -l$new_pane_height $EDITOR -c "$change_aucmd" -c "set ft=jq" $query_file
nodemon -q -d 0.3 -w $query_file -x "$nodemon_cmd"
}

dependencies: vim, tmux, jq, nodemon

[1] https://github.com/simeji/jid
On a different note. I made my own laptop stand out of carbon fiber because I wanted specific things that I couldn't get out of the store. I am a digital nomad and finally build the thing after 4.5 years of country hopping. Got lots of interest and now working on a production run: https://www.fiberstand.com :)

Software wise, mostly scrapers for classified ads ect.
I wrote a small script, executed with a cron job, which adjusts the color temperature of all my Philips Hue light bulbs throughout the day.

The Hue device bridges have a simple HTTP api available over the local network, and with a combination of curl and jq it was easy to retrieve the IDs of lights that are currently on, and then set their color temperature.

I've since moved the functionality into a small service I wrote in Clojure that runs on a Raspberry Pi, as part of an effort to consolidate a few different things under one roof.
If you have multiple federated clusters you can tolerate issues that affect an entire cluster of machines. Having 3x clusters each with 3x master nodes that do not depend on each other, and Volume drivers that are aware of having replication across regions, you can make some really reliable things.

For most use cases though what you're talking about will work and you can do it today with just setting up a VPN to have a flat internal network topology.
Subatomic particle seen changing to antiparticle and back for the first time
Original article (with link to PDF): https://advances.sciencemag.org/content/7/24/eabe4577. I do not know much about testing mice in this study's context. In light of my unfamiliarity, I am astounded that up to 20mg/kg of morphine can be given to mice without fatally suppressing their respiratory drive! If I give a (human) patient even 1mg/kg, I am likely to kill them in absence of airway/respiratory support (not to mention their likely markedly reduced BP). Maybe I am misreading that which I am unfamiliar with. Fascinating, regardless!
I created this tool for fun to experiment with my raspberry pi

Its a tool that allows you to run server commands via text messages

https://github.com/mtdevss/server-text

Its a fun program to play around with
The only time the sizes attribute is not needed when using srcset is when the rendered size of the image is fixed.

One example would be a logo that is less than 320px wide (so it fits even on mobile). In that case you can add x descriptors to give a higher quality logo on retina screens. e.g.

<img src="logo.jpg" alt="Logo" srcset="logo.jpg, logo-2X.jpg 2x">

Alternatively use an svg :)

But if the image depends on the viewport width then 'srcset' (without x descriptors but with w descriptors) and in combination with 'sizes' is the way to go.
If it’s my thing and I don’t agree with how you’re using it - 100%. Particularly if you’re (for instance) spreading medical misinformation during a pandemic.

Not sure what your point even is here any more.
I'm sorry for the experience you've been having with support and 2fa -- we're actively investing to improve the story on both of those.

Capital One support has been minimal in the past, but it actually should work MUCH better now that we've switched to supporting them via OAuth. If you are having any problems moving to the OAuth implementation for Capital One, or if you have switched to OAuth and are still having issues, please feel free to reach out to us at @Plaiddev and we'll be happy to help you work through it.
It's a real pain. I work with lots of "data science" types who are often trying to concurrently learn JavaScript and d3 - often with JS as their first or second programming language. It's difficult enough for an experienced programmer coming back to d3 after a few versions to pick out what's d3 vs. what's Observable - and very difficult to help a relative newbie through the process of turning what's shown in an Observable notebook into something that can run in an ordinary web page.
Last time I used Qt, it had classes to abstract hardware.

Stuff like QSerialPort worked fine across platforms for my usage. YMMV
I should read more Poe.
> 1. GUI vs. CLI - I want to support both. But should it be a CLI first application that's then wrapped with GUI? Or perhaps it's better to build it as a GUI first application, and add a CLI interface to it? Or just have a core library, and use it in independent CLI and GUI tools? I never wrote a cross-platform tool, so I am not sure what's the best approach.

Don’t be GUI-first or CLI-first; be API-first. You can get started by writing a test target. As soon as you need more than “edit tests, recompile, run, examine debug prints”, you can start on both the GUI and the CLI together.

Focusing on keeping a solid API makes things much simpler. And if you ever regret choosing Electron over Qt or vice-versa, having all the juicy parts behind an API makes it much easier to switch.

For examples, look at Git, the TypeScript compiler, and Everything [0] (closed source unfortunately).

There was a quick-search app for macOS that used V8-to-Rust asynchronous procedure calls as the API. It would make a great example, but I can’t remember it’s name.

(Love the app idea btw! I look forward to trying it on my mess of files for my small business.)

[0] https://www.voidtools.com/support/everything/sdk/
IIRC there's also a per sink device signature verification scheme inherent in the protocol as the devices check in to Google's backend that makes it nearly impossible to just spin up arbitrary sink devices. Google has to have known about the device's public key before they'll talk to it, and it requires their backend fundamentally to work. That key association is probably a manufacturing step that we're not privy to.
Did you consider wxWidgets? I chose it over Qt and Electron for a recent project, because it gave me the most native looking UI across Mac/Win/Linux, and resulted in a small binary size and memory footprint. The project was an SSH file browser. Sounds like your project is also file browser related, so you may be able to get some inspiration or even reuse parts: https://github.com/allanrbo/filesremote
The Access Act Takes a Step Towards a More Interoperable Future
The article actually doesn’t tell the true horror of the situation which is this:
Companies burn out employees and then deal with the consequences by firing them or bullying them into quitting. Employees lie about how their last job ended and limp into the next one, using the unemployment gap to recover as best they can.
There’s a deep understanding of the tools they use every day. They may use a framework as a starting point, but they also understand the JavaScript that makes the underlying work. They leverage CSS like a fluent language, manipulating DOM elements to their will. They see browser APIs as the foundation of their process rather than puzzling concepts pulled from Stackoverflow answers.

I wish that were true, I have not seen this in the corporate world and it appears absent in the job opening details of startups.

My experience tells me this:

* If you are really good you can be up and running a new project in something like React in 2 or 3 days.

* If you are really good you can be up and running without any framework at all in about 2 weeks.

* If you don’t use a framework you are forced to make tough design decisions early. This is critically beneficial and pays interest over time. Those decisions allow you to scale in ways frameworks cannot.

* The value of frameworks is over estimated for the wrong reasons and under appreciated for reasons developers don’t immediately see.

* Working directly to the DOM (even without query selectors) is amazingly easy, but it takes practice (just like writing CSS). The value is not the data, but the relationship between the nodes. That line of thinking reminds me of this board game called Othello.

* State management is less easy but still not challenging. https://github.com/prettydiff/wisdom/blob/master/state_manag...
Would you freedom be harmed from somebody's public gathering? How in the world?

I think you are doing philosophy here.
Skull has more going on for it than it seems like it should for its super simple components, but at the same time I only ever seem to play it with 6 players, and the game feels to me like it outstays its welcome after about 20-30 minutes and those 6 player games always seem to take 45 minutes to an hour to play out, at least with the various groups I've played it with. I'm usually pretty bored by the end of it.

Coup, while more complicated, is a similar game that never seems to last that long, even with 6 players (usually closer to 10-15 minutes for that).
Basically this is the concept of stackoverflow. People (hopefully) post their error messages and then others answer.

That being said if it could so easily be answered, then one might wonder why it the computer doesn't fix it for you? I would suggest that there is often sufficient ambiguity about what the programmer desired that the compiler (or other tools) cannot just correct it.
> They see [XXX] as the foundation of their process rather than puzzling concepts pulled from Stackoverflow answers.

Apart from front end, this in general is the mark of people who are fun to work with. Especially so when the XXX in question is something I don’t have facility with myself.

I’m very glad that programming has become less an obscure art known only to the adepts. Nevertheless I personally prefer to work with those with deep knowledge of their domain.
The Nix properties fit ideally with the domain it tries to solve:

- functional with no side effects (for the same imput you always supposed to get the exact same output); derivation is function of its inputs (e.g. source code, dependencies, compiler flags, architecture and so on) if none of them changes you're expecting to get the same file. Introducing side effects would remove this guarantee, and introduce bugs.
- lazily evaluated - you can specify multiple things but Nix will process only the ones that are referenced, this makes weird experience that the code isn't executed from top to bottom (as most people would expect)

Those two things essentially makes the derivation declarative. You specify what derivation you want and what it needs (like dependencies) you can also use the language to transform the inputs to the way you like and still preserving the guarantee that if one dependency changes the project needs to be rebuilt.
No. Five-year-olds can't do particle physics. It may as well imply nothing at all.
> Oh hi, my dubious life choices have been such that this is my specialist subject!

Interesting humblebrag. Other than needing to learn command line what is the author referring to here? Learning the order of operation in a commonly used command line isn't something to be so proud of.
I made HackerCards(https://chrome.google.com/webstore/detail/hackercards/ncblkm...) to easily skim over HackerNews on chrome new tab page.

Another one is Hijri for Chrome(https://chrome.google.com/webstore/detail/hijri-for-chrome/m...), a Hijri date viewer that too made for myself for tracking ramadan fasting count.

And yes my own Chrome theme 'Space Grey'(https://chrome.google.com/webstore/detail/space-grey/cohabkm...)
Codecov ditches Bash Uploader for a Node.js executable
You mean a forum populated by people who act like they think they are on the high end of the IQ range
Here in the US all the big supermarket chains offer either a drive-up service (where you drive up and park, and the order will be brought out to you and loaded into your vehicle), or full delivery to your door.

As a single parent this service has been absolutely wonderful. It saves me at least an hour a week, and keeps me from impulse buying and blowing my budget. I can schedule the delivery for a one-hour window when I know I'll be home, and the quality of the produce has been excellent.

I pay a yearly fee for unlimited deliveries (I only use the service once a week), and typically about a $10 "tip" to the delivery driver each week.
I'm not surprised the number is so low. Isn't it the case that only 1% of people cause 99% of the content or something? It'd be only a small number of core intentionally malicious actors could cause other people to follow along in good faith, especially in today's social media pressure to speak on controversies.
This article reminded me of an excerpt from "Diary of a Bad Year," where J.M. Coetzee complains that the insistence on accuracy and objectivity in sports officiating represents an anti-social, inhuman attitude toward sport (think about why many people find the prospect of robot umpires in baseball distasteful). Coetzee suggests that this trend began in horse racing because bettors had money riding on the outcome, and that demanded accuracy.

It's tempting to think that the "refinement culture" that Skallas is talking about, which encompasses everything from hyper-optimized athletic training, to corporate mascots rebranded for sex appeal, is similarly motivated by what is, at base, just capitalism.
I built a music player for videogame music formats because the only other player on MacOS that supported them had a terrible UI and didn't support all the formats I wanted. I consider it a tool because I use it a ton during work to play infinitely-looping songs to help me focus.

https://www.mkelly.me/moseamp/

The progression of me building the app was (over a span of maybe 7 years):

- Prototype compiling GME[1] into asm.js, generating sound samples on a webpage, and piping them into the Web Audio API.

- Turning that prototype into a desktop app in order to learn Electron.

- Giving the desktop app a proper UI in order to learn React + Redux.

- Switching to a native node.js addon to fix slowdown/memory use during playback.

- Switching to musicplayer[2] so that I could play Playstation music.

- Adding a Windows build so I could listen to music while coding on my Windows computer with the same UI as on MacOS that I had by now grown accustomed to.

- Adding a visualizer to learn how, well, visualizers work.

- Adding a piano-roll visualizer for NES music and rendering-to-video because my friends who make chiptune videos on Youtube use an old, inflexible program to make their videos.

I would say the number one driving force is that I made a tool I use pretty much every day; tools I've made that are only occasionally used never really motivate me enough to bother fixing them up, but with Moseamp every fix is an _immediate_ improvement in my day-to-day.

[1] https://bitbucket.org/mpyne/game-music-emu/wiki/Home
[2] https://github.com/sasq64/musicplayer/
BP (when properly explained) emphasizes that the important aspect of the timeline is its relativity to the current time.
The First 'Google Translate' for Elephants Debuts
I've taken these spare time gaps to do work like things at work but that have lasting value beyond my work day/week/role.

For example I'll read books.
I find the production of bad movies to be such an interesting issue. Lot of money, lots of highly skilled people, long time, it still some how you get really bad results fairly often. It is a lesson in humility for any ambitious endeavor I think.
Having gone through two of these (one shorter and the recent one much larger), I think the best thing anyone can do for themselves is make a "break glass in case of burnout" plan where they save up margin during the good times so that when the famine hits part of the stress isn't the painted-in-corner feeling of "I need a break but have no margin to take one"

Ultimately the answer is always simple and involves protracted rest - deload, de-stress as much as possible, and recover. 6 months preferred, but 12 months for major crisis' is nice to have in your back pocket.
Neural networks are just the printing press for correlations
> life has innate value especially since we're the only intelligent species we know of, even if they aren't valuable in a capitalistic sense

I personally agree with you in general, but I'm talking about a self-image formed through extensive socialization to the idea that work == value. Even if in some abstract sense all intelligent life is a gift, the "waste of oxygen" label starts feeling appropriate as your cohort materially advances without you. I guess I was unclear in that I wasn't going for lifestyle judgmentalism; more trying to explain the negative self-image that's easily developed given capitalist socialization and a lack of capitalist success.

> It can be uncomfortable, sure, but if you can get past that...

Again, I agree in general, and there's obviously a spectrum of how impacted any particular individual is going to be, but I think you're underestimating the degree of psychological scarring that can be built up over a long time in the pit. That step of admitting that you're the problem is one many fight against for years, which happens to be linked to self-deception around how fun/fulfilling the consumption-only life is. I guess I'm glad that you've got as hopeful of an outlook on this as you do, but I want to temper that a little with the understanding that "well, just go get a job lol" is akin to "well, just stop being sad lol" - in both cases there's probably a lot going on that simple willpower alone isn't going to fix.
>My point is you can either give a shit about your job or not. If you don’t, don’t expect to do anything innovative or produce a lot of value.

You seem to have conflated working overtime and not taking vacations with "giving a shit about your job".

Sure, not giving a shit about your job wont give you innovations. But working overtime and not taking vacations wont give you innovations either. It's totally orthogonal (if not detrimental to healthy worklife and innovation) issue to whether you're passionate about your job or not.

Case in point:

(a) No innovations come out of the hundreds of millions of Americans who work BS jobs, think them as BS jobs, but still being culturally or openly forced to work overtime and to only take meagre vacations. No innovations come from office drones who share all that, and Japan has not made any dent in CS/IT, despite working even more and having worse life balance than Americans. Working overtime is good for production lines, mindlessly churning out stuff.

(b) Innovations come just fine from companies with a healthy work-life balance. Heck, most of the great CS and IT innovations, that in substance and impact no FAANG or BS "unicorn" ever matched, came from places like IBM, Bell Labs and the Xerox Parc, of the 60s and 70s, great places to work, with good work life balance, and research focus -- not toxic overtime environments.

The idea that innovation and liking your job is not compatible with worklife balance or EU-style vacations, is a toxic and dangerous to humanity (ito ndividuals and their families, for starters), idea.

It makes for good profit and docile workforces though. Whatever makes the US employer sleep well at night...
>the odds of someone taking actual BTC as payment are pretty low right now. It's way, way more likely I can just use another credit card company, a debit card, Venmo/Cash App/PayPal, etc. I think this argument, while common amongst BTC folks, is pretty hypothetical.

It's the only way you can buy a 4chan pass for example

https://www.4channel.org/pass

>The problem with this is that we'd lose lots of the tools we have to fight organized crime

Well right now we have bitcoin where there is high anonymity and the government has no power over. In a government payment system they would have the power to freeze accounts and track transactions. I don't see how that's a worse system in regards to fighting crime.

>I was trying to focus on your claims about 1A

You completely misunderstood my original claim and went on a tangent bringing up common talking points. As if it were a knee-jerk reaction to seeing the words "corporate censorship" and "first amendment" in the same paragraph. I'm still not sure that you understand.
> PWM is one of two ways to dim a display; the other is by changing the voltage of every sub-pixel—the analog method. LG uses this approach to adjust brightness for its OLED TVs.

These sentences are confusing to me. Am I correct to understand this as saying that LG uses “the analog method” to dim the TV displays (and not PWM)?
No, the purpose is to make money.
Not sure why you were downvoted, but perhaps they were thinking about Redis transactions (lua scripts that can do multiple operations at once). If Redis is your datastore (groan), then you can transactionally enqueue tasks with your unit of work.
I built a redis AOF rewriting toolchain to undelete keys at specific points in time because I was working with people who picked a storage engine without consistency guarantees without understanding the consequences. The tool will trace the lifecycle of a key through the AOF and all events attached to it so you can pick an event to “undo”. The output is a bunch of commands to recreate the key in the state you need it in.

I’m not publishing the source because it’s extremely dangerous and not very well tested. In the wrong (or right but with misunderstood intention) hands it can make your day worse.

It works by iterating through the AOF, filtering all commands related to the interesting key and replaying all commands except matching ones into a standalone instance of redis. Then it dumps the key that is left.
This is pretty drab. I can be up and started in about two minutes with React, typescript and parcel.
That’s the difference between all the integers (from negative infinity to positive infinity) vs just the natural numbers (from 0 to positive infinity). You can have infinitely many guests starting from a particular first guest.
So it saves 2 characters compared to ###y ago but requires an explanation.

2500 BP
2500y ago
I've built a tiny dependency installer targeted at old systems / clusters where you need to bootstrap modern libraries and tools from an old GCC.

It's very small, just a few lines of Bash.

https://github.com/W4RH4WK/DIFAS
There’s been several dissertations on this topic and a lot of research tools. Compiler errors are [slowly] getting better.
Then just don't respond homie.
ZeroTier is incredibly good. I have a Synology too and without ZT it would be a lot less useful.
My IT guys at work somehow keep disabling the show hidden files and folders feature in windows 10. So I wrote a program that checks every 5minutes and turns it back on lol
What about in terms of number of requests and requests per second?
They say a skunk can't smell its own stink. The true test will be when you are around people who aren't around you most of the time.

But I've read that your experience is essentially correct - mostly the stink comes from the subsequent bacterial battle over the newly "disinfected" territory. Left to their own device, the bacteria that your body has learned are beneficial eventually win out over the ones your body has learned are hostile again.

Likewise they also say over-reliance on mouthwash leads to halitosis for exactly the same reason - displaced beneficial bacteria colonies.

We even use this knowledge in its reverse: probiotics are beneficial, and purposely supplementing them in our gut (instead of just wiping them out over and over again) theoretically displaces harmful bacteria and fungi.