HN user
Author here. SXO + Reactive Component offers a middle ground between full hydration and static HTML. By rendering semantic server-side JSX and using a 4.8KB client library to provide signal-based reactivity.
I'd love to hear what you think about this approach for web components architecture.
Q|ery uses SQLite and QuickJS, too, but in Rust.
Documentation is an essential part of software development in the open-source world. We all know it's crucial, yet somehow, it always ends up as a collection of outdated markdown files and half-finished README.md lurking in our repositories. That's exactly why Query Docs exists—not to reinvent documentation but to make it actually work for both contributors and developers.
Hey, Query [1] creator here. The article raised some exciting challenges. With Query, we solve booth downsides mentioned in it. To keep things simple, we use EventSource for live reloading [2] and JSX Server-Side Rendering [3] for those who want component reuse in the server. It's just JSX with some helpful extras. I'm happy to elaborate on the technical decisions if anyone's curious.
A couple of days ago, I wrote an article about it: https://dev.to/gc-victor/building-static-html-pages-with-jsx...
[1] https://qery.io
[2] https://github.com/gc-victor/query/tree/main/examples/minima...
[3] https://qery.io/docs/modules/function.html#jsx-server-side
Donation link: http://magit.vc/donations.html
Is or was? The article explicitly mentions several of her tracks as having come from the pop production machine.
Thank you for posting this. Fine work. I need to give it another read later, but for now, I find Thomas' iambs a little heavyweight. Every line has the same 4x(ba-DUM, ba-DUM) rhythm, with almost no variety. Frost has a lighter touch with meter.
A nasty workaround for a problem which should not exist in the first place. Ditto dependencies on private repositories.
Is it hard essentially, or is it hard accidentally?
Not exactly either, but certainly a bit of both. Programming is hard primarily because it is so poorly understood. The entire field is in its infancy. Comparing it to art, I'm pretty sure we haven't even reached the "stick figures scrawled on a cave wall" stage yet. As Alan Kay pointed out we sure didn't invent an arch yet: http://squab.no-ip.com/collab/uploads/61/IsSoftwareEngineeri...
It's nice to see the Eve team trying to do something at least slightly different from the same-old, same-old. Even if it looks a lot like some horrors of yore (FoxPro) when I squint.
That's fantastic! If you don't mind me asking, how old is she? University student or younger?
If you didn't catch The Economist's biases on a cursory reading of one issue, that's on you. Simply skimming one of the leader opinion pieces and comparing it to, e.g., a Krugman column, should tell you that the authors would come to blows.
Besides, what is an "orthodox" position? Whose?
The obituaries are brilliant. One of the best things I read every week.
Recently? The Times has been acquiring credibility question marks since before it unquestioningly published the nonsense about aluminum tubes in Iraq.
Your comment simply says that your politics don't align with The Economist's.
I personally find the "he said, she said" style of reporting that purports to give a fair account of all sides intolerable and hypocritical. It often allows complete idiots to air their opinions in the name of presenting a "different" view. This lets the reporter subtly influence the reader while preserving the illusion of impartiality.
The Economist is a highly biased newspaper. Unlike nearly all other publications aspiring to high-brow status, it displays its biases openly.
Not entirely. Team control is a major part of it for companies, and history makes a huge difference to the experience. Slack servers allow the use of IRC clients, but I gave up on Colloquy almost immediately after seeing the benefits of history. For the right teams, the IRC+history combo can almost completely eliminate email use.
Also, Slack bought a company which did voice, video, and screen sharing. Since join.me went downhill, this will be a welcome addition to Slack.
On the subject of IRC: it wasn't fading all that strongly, IMO, at least for open-source and free software discussions. Then Slack came along. Startling to see a proprietary clone of IRC (albeit with some nice extra features, namely history) come along and start taking over. See, e.g., the Clojurians Slack community.
Your surgeon is lazy. He wants you as a patient for 2 days for his fee, not for two weeks. All my research indicates that PRK is substantially better.
One thing about this case puzzles me, and none of the news coverage I found explains it: what code did he actually take?! Details matter. Was it a tweak of something like Samba (obviously GPL)? Or was it part of a proprietary risk management system, derivatives models, or other direct money-making programs?
If he took the former, then I'd side with him — he took nothing of genuine value. If he took the latter, then, très uncool. (I witnessed several incidents of model theft while serving time on Wall Street in the mid-2000s, and none were publicly pursued like this one.)
English has an equivalent: "it is what it is". It also stops solution-seeking dead in its tracks. A hateful little phrase.
Sure. I added some reading material links to my comment. The Rane document has an OSHA safe sound levels table at the end, a good reference. Keep in mind that the dB scale is logarithmic if you want to crunch numbers on device power, headphone sensitivity and impedance, and resulting SPLs.
The rules of thumb about "60% of maximum volume for 60 minutes" and "if you can't hear your surroundings, it's too loud" are nonsense. Dangerous volume settings depend on a headphone's sensitivity, the output device power, the headphone's isolation ability, and the recording. These parameters vary. Wildly.
A well-fitting isolating IEM can slice off 25dB of noise, more than enough to (mostly) eliminate background conversation noise at any location short of a hip restaurant. These IEMs tend to be so sensitive that they become earsplitting at a tiny fraction of the maximum output volume, way less than 60%.
Learn approximate dB levels of various sounds, compare various noise with a meter (even an uncalibrated app will give you a ballpark idea of what you're dealing with), and listen to music at an average 65dB or less (this will obviously vary with dynamic range of your music; occasional 80-85dB peaks won't kill your hearing).
One trip to a dance club or rock concert without earplugs (100-110dB on average in my experience, 120+ has been known to happen) will do more hearing damage in a few minutes than a lot of headphone listening while working. I'm pretty sure the busy street near my home routinely hits a 90dB average at rush hour, solidly in the danger zone compared to reasonable headphone use.
Edit: To learn more, read the following:
A huge number of soldiers returning from the war had been handed 25-year (in most cases equivalent to life-long) sentences under the 58th article of the Soviet penal code (see http://en.wikipedia.org/wiki/Article_58_(RSFSR_Penal_Code) — the Soviet Union officially had no political prisoners, only criminals). For the most part, their crime was contact with other Allied troops, so it was easy to accuse them of contact with the West, and eliminate any dangerous ideas they could have brought into the bright nation of the dictatorship of the proletariat, the heaven of the working man. These people would have been serving their sentences through the 1950s, and Khruschev's rehabilitation policies (far from popular in the Politburo) did not start until 1956.
Instead of banning specific tools, try promoting officers and enlisted personnel who do a good job, including public speaking and presenting ideas.
Life imitates fiction? Jack London wrote a short story (part of the Smoke Bellew series) about something similar:
I think Ron was referring to the development process, rather than the finished program. The way Lisp languages and environments handle REPL-based interactive development is significantly more powerful and flexible than e.g., Rubython or even Haskell.
Modifying a running program to make a change as you develop it is an incredible speedup, relative to (recompiling and) restarting all the time, and even relative to reloading whole changed files.
Ulysses is definitely doable, but it marks a point when high-brow literature stopped being something every reasonable, intelligent, and educated person enjoys reading. It's a chore (less so than FW, of course), and of questionable value — yeah, it's cool to get all the references to Homer, etc., but I don't think anyone puts down Ulysses with anything other than a sense of relief of having scaled it as an obstacle. (Yes, I studied Ulysses. Voluntarily and on my own time. I don't mean to belittle Joyce's talent. Ulysses is obviously a huge accomplishment, beyond nearly all writers.)
Compare that with, say, Dickens. People would drop what they were doing to read the next installment of Little Dorrit.
This happens over and over again.
Oh no, the Sea Wolf works, but is too expensive at $2B/boat! Let's scrap the working program, use "lessons learned" to build a cheaper attack submarine. Years of delays and cost overruns follow, and we get the inferior Virginia class, at a bargain-basement price of $3B.
Oh no, the F22 works, but is too expensive at $150M/plane! (Would have been less over time, but who's counting?) Let's scrap the working program, use "lessons learned" to build a cheaper fighter. Years of delays and cost overruns follow, no working plane in sight, but if it ever flies, we will get the inferior F35, at a bargain-basement price of $350M/plane.
I can't wait to see what happens when the Ohio-class replacement program starts for real. Also can't wait to see what happens when healthcare is fully nationalized — I'm sure the bureaucracy in charge will be so much sleeker and more efficient than the Pentagon, and special interests so much less influential in Congress. Oh, wait: annual US military spending is about $750B, and healthcare adds up to $3.5T.
Previous discussion: https://news.ycombinator.com/item?id=7913183
In classical Latin texts, I remember running into a lot of sentences which start with "itaque" (which means "so"). The habit hardly started recently.
I consider the zsh scripts a proof-of-concept more than production code. It should be a relatively simple matter to rewrite the gpgd scripts in a portable manner, provided gpg and tar are available. I'm sure Windows has some kind of secure rm equivalent, too.