skysight-inc/HackerNews huggingface dataset:
Is there a way to render the org table without using a source block?

This is what I did:

- input the defun for create-summary in ielm

- Added tables like the ones in your link. NOTE: I used different numbers.

- M-x create-summary runs but it just echoes some messages.

- I put (create-summary) in my org doc, then ran C-u C-x C-e and it returns the lisp representation of the table:

(("Team" "Hours") hline (#("Team 1" 0 6 (face org-level-1 fontified t)) 30) (#("Team 2" 0 2 (face org-level-1 fontified t) 2 3 (face org-level-1 fontified t) 3 6 (face org-level-1 fontified t)) 60) hline ("Total" 90))

- Then, I put the lisp object in a variable in source block, eval'd it and got the table:

#+BEGIN_SRC emacs-lisp
(setq x '(("Team" "Hours") hline (#("Team 1" 0 6 (face org-level-1 fontified t)) 30) (#("Team 2" 0 2 (face org-level-1 fontified t) 2 3 (face org-level-1 fontified t) 3 6 (face org-level-1 fontified t)) 60) hline ("Total" 90)))

x
#+END_SRC

#+RESULTS:
| Team | Hours |
|--------+-------|
| Team 1 | 30 |
| Team 2 | 60 |
|--------+-------|
| Total | 90 |

I was wondering if there was a way to generate the table just by running a function.

Got the idea to use a source block from here: https://stackoverflow.com/questions/65950060/converting-list...
You make a statement without reasoning or examples: empty argument.
You are not arguing any more, just want to be right.

> This is the "texbook definition"

The textbook definition of gravity is F=Gx((M1xM2)/r2)

According to Newton's textbook.
Ask today's physicists about this.
For some reason I'm getting scroll bars on some of the text fields in Firefox[0]. It's not just your site, I notice them on other sites as well like on Reddit[1], so maybe the fault lies with Firefox or even just my installation.

[0] https://imgur.com/NYQYEOK

[1] https://imgur.com/HUJrgm7
Amazon is in trouble if it can't come up with revolutionary Machine Learning product on par with OpenAI's ChatGPT
Our Hermes was created 6 years ago, and now there's one everywhere cry cry
Good one! Very funny!

/me remembers years of being gaslit by Gophers, of all stripes, for asserting that, no, unlike the cult of personality around Go, i did actually know what i was talking about when I said GOPATH was a nightmare in real world use (even better, it was plainly obvious even with pre-1.0 kubernetes). Just cringey.

For all the handwavey whinging about Rust, Gophers have treated me far more poorly over things that have been retconned and forgotten years later.
I'm at the point where I want to see docs on any non-private properties/fields, methods, parameters, classes, etc.

I think there's nearly always value to be added:

* Explaining required fields, if null/blank/0 is allowed, where an ID comes from (db vs app-generated), if string values are formatted or require formatting (credit card, phone numbers), max length or other restrictions

* If a class/method is thread-safe or not (when not obvious and misuse is dangerous), error conditions, timeouts.

* Any external or indirect dependencies for use (config, packages, etc)

* Links to other docs/wikis or tickets is hugely useful.

When you're writing/working on the code you already know all this stuff, and it takes only a couple minutes to document. When someone else (or you, 6 months later) comes along to use or modify it, figuring everything out from scratch can take hours -- or worse, bug reports from QA or customers. Docs shave this down to seconds and directly avoid bugs.

The other huge benefit I often experience is through trying to write docs for something I realize there's a better, more obvious name that makes it easier to use and requires less explanation (less docs). This happens on easily 5-10% of the things I write docs for.
Or maybe, just maybe, Google is responding to the recent string of mass shootings.
I write GNU-ChangeLog-style commit messages which mention every function and other named entity touched, added or deleted, with details about why. Between that and the diff, you can figure out exactly what was done and why, matching the comment with specific code blocks.

I've never been disappointed when digging back in history to figure out why the heck something was done.

It would be a strawman of my position to say that I'm favoring zero comments. For instance, a /* fallthrough */ comment in a C switch statement cannot be in a commit comment, not the least reason for which being that compilers look that that nowadays.

Comments should be like road signs. I need a warning about a dangerous curve ahead, not a discussion of why it was built that way.
I'd say it's more like someone who has a successful restaurant learning to wash dishes. Adding a website to an already successful business that can manage without one is very different from basing a new business on a new technology.
i mean, this is actually perfectly clear—in the sense it’s clearly and obviously a mistake either with the comment and function name or it’s implementation. the example isn’t great because it’s devoid of context that might indicate what specifically is wrong with it.

there are many standard means that should catch this: code reviews, unit tests, etc.

this stuff can obviously still sneak through, but i don’t think this is a good example of what folks are generally talking about here.
Clang implements nearly all GCC extensions. (No nested functions.)
Being unable to middle mouse click knives to open new tabs is a usability dealbreaker for me. Wrap the image with links, not binding awkward events.

It'll also reduce your load a bit, as I won't have to continuously reload the grid page of 50 knives just to look at one.

Some other suggestions:

* If I search handle material "micarta" I get a whole bunch of distinct incarnations, like "micarta, ash wood burl" and "bone, micarta, wood". Tokensise each term in the material type and return them as groups. "micarta" should have both of those, as should "wood", and ofc "bone" would distinguish them.

* For brand search, populate the list alphabetically or something. It's nice to have a list to scroll to explore. I have no idea what options are available other than a few brands I already know. If the goal is to find and explore the 60k knives there, I need some help.

* Sanity check the knife stats. There are going to be zero knives with a blade thickness of 1", nevermind 5". An example of one that shows up here is this knife: https://www.knifegeek.io/blades/boker-121589 which I presume you scraped from here: https://www.boker.de/en/vollintegral-2.0-jaeger-gold-121589#... but you should maybe have a secondary scrape for stats that are impossibly beyond params. Here seems to have the correct blade thickness: https://www.knifecenter.com/item/BO121589/boker-jager-gold-v...

* From the knive page, present tags to re-broaden the search. Using that same knife example, the navigations is currently: `Blades -> Boker Jager Gold Vollintegral ...` which is useless. It's a knife in the category of knives on a knives website. I'd like to be able to navigate back by type / brand etc.

It helps the exploration. I might find something I think has nice features and want to explore that set more.

* An obvious one I'm sure you have planned, but there are much more crucial and interesting features than the ones listed for filters. I care far far more about the general style of knife than I do blade thickness or handle material.

Fixed vs folding vs others is ofc vital.

Within the category of folding, the type of lock, if any.

Blade shape, a no brainer.

Nice to have overarching categories too. Rescue vs dive vs bushcraft would help immensely.
Well somebody doesn't have a clue...

In camera HDR: https://www.slrlounge.com/in-camera-hdr-intro/

In camera focus stacking: https://www.youtube.com/embed/E5zX1E5wAiE

Sometimes high end "pro" cameras will skip those features because they expect people to process those image on a computer anyway, but in general a modern camera will beat a phone hands down.
Or Intel has found cover from other tech shops to 'do the necessary' and prune the dead wood. It's about time the C level began to look at employee performance and contribution to profits or losses.
You can get cans without the bitterant, but at slightly higher prices... which incidentally makes a great refrigerant too.
How can you be sure the new owners/management of Twitter and the hired "investigative journalist" are not compromised? I was very symathetic and enthusiastic about their recent pivot toward free speech. But now it's clear to me it was not about free speech but rather a certain agenda which is suspiciously aligned with Russian interests.
Well that’s both funny and a real point. I did try to make the idea resistant to such points of fact with the “or whatever” clause in my post, but your concise reply made me chuckle.
Great point. Prop 13 creates a lot of illiquidity/friction that probably keeps people in places they wouldn’t stay in otherwise. Not just old folks. It’s probably just as much of a problem for people who inherit property or get a job an hour away.

Prop 19 passed in 2020 IIUC partially solves the problem you mention because people 55+ can maintain lower tax rates after moving, but of course it is just a bandaid. Definitely the better solution would be for the real estate market to not be so expensive that people can’t afford to move/live in the general type of housing they want though.
Yet they don't...to be fair.
There were countless attempts to extend or replace SQL:

OQL: https://en.wikipedia.org/wiki/Object_Query_Language
UnQL: https://www.dataversity.net/unql-a-standardized-query-langua...

More modern:

PRQL: https://prql-lang.org/
Malloy: https://news.ycombinator.com/item?id=30053860 (it is so obscure that Google replaces it to "Malay language")

Another example: ClickHouse supports standard SQL with many features such as window functions, SQL/JSON, and extends it to make it convenient for data analysts by adding: - higher-order functions; nested data structures, arrays, tuples, and maps; aggregate function states as first-class citizens, unrestricted usage of aliases in any place of expression, etc.

https://github.com/ClickHouse/ClickHouse/

I'm an everyday user of ClickHouse, and I'm finding its SQL implementation the most pleasant to use! Although it's unsurprising, because I'm also one of its authors... I'm also welcoming innovation and improvement of SQL without the introduction of a completely different language.
No way would I accept a pay cut. Intel is a terrible company.
> countries that are generally wary of Chinese power and might become our de facto quasi-allies in the future (like Vietnam, Indonesia, and Thailand)

Aren't all three in Belt and Road?
More generally... my unwritten article is "Reducing developing bad beliefs about code by not listening to Uncle Bob".

He has been trying to say profound things for a long time now. He was super active in the XP community in early 2k onwards and he was nearly always saying things that I felt were a bit "off". i.e. there was a gem of an idea, but the idea was turned into some principle or rule that lacked nuance and context. Reality is, there isn't any fundamental rules/principles... just ideas, some ideas seem more universal than others, but these ideas are just a bunch of strategies you can use when approaching software development and depending on context they may or may not be good strategies.

In terms of commenting, some of this weird "wisdom" around commenting was fundamentally rooted in the idea you can't fix bad code with comments. People noticed that a lot of times where there was comments in "poor" code it actually was a spot where you could do some kind of refactoring to make the code clearer. Eventually this morphed into "If you need to comment your code you have failed" type sayings. However, there was plenty of people advocating commenting to explain things the code can't tell you, but too many were swayed by "commenting is failure to write good code" that they threw out some of the reason why people like to put comments in. Many in their first 10 years of coding really want guidelines and rules and principles and argue strongly for things they have found effective compared to how they approached coding previously. But these things you learn are almost never universal, even if you can see/argue how you could apply it to all kinds of things, other approaches might actually work better, or might work better in different contexts.
"Hi marketing department! You're losing 50% of staff and 80% of advertising budget!"

bam, growth -> profitability!
classic HN hivemind opinion regurgitation
I thought it was an Australia thing but yes, $1.50 pipes and $3 fittings are the norm here too. Fortunately, you can 3d print fittings which opens up all sorts of possibilities that don't really make sense for use in plumbing.

https://www.thingiverse.com/thing:2956356
C is a language with a specification which defines it in terms of a virtual machine, not translation to machine code. The memory model is also totally different and it has lots of undefined behavior.
I have a sneaking suspicion that the people who profit from IP law are of course going to tell you that it's the greatest thing since sliced bread and that we couldn't have solved COVID without it. For the sake of discussion I'll concede the point that IP laws are a necessary part of innovation but that brings up a major question -- how much IP law is optimal?

Do we have an optimal amount of IP? Who decides? Why them? What metric do they use? How do we disentangle the conflict of interests between the people telling us we need more IP and the fact that they make gobs of money off of it?
How to Create a Playroom That Appeals to Children and Adults
You might slow down but that’s offset by the roads being it’s inherently unsafe. Real world statistics frequently show such designs underperform compared to the expected payoffs and sometimes reduce safety.
What? No, doing it by population is a bad approach.

Land is the resource you're dividing up. The question is how much of the divided-up land is allocated to an (allegedly) niche usage.

Doing it by population is like saying "almost no one is a billionaire, almost everyone is basically poor and equally-poor, so there can't possibly be a wealth inequality problem". (I'm not saying there is/isn't a wealth inequality problem, I'm only saying that's a dud argument.)
Elon is to Gollum, as Twitter is to Ring?

"My Precious!"
i think what gets missed is that it depends. there are languages and domains where it is possible to write sufficiently succinctly and clearly that you don’t need comments.

there are also places where you might want to explain the “why” even if the code is clear.

relying on comments to understand the “how” has been a smell in every codebase i’ve seen.
Nah. Its accessibility at this point and its time we start talking about it, yes, even here. The internet is being ruined by js and screenshotted or otherwise uncopyable, inaccessible text.
It means that customers that don’t care for ECC aren’t paying for it. If you want ECC the option is available, at the cost of a few GB storage.

If we had this with desktop hardware it might even be preferable to standard ECC for workstation type use as it doesn’t require ECC DIMMs.
On my first trip to the US, early 2000s, my business partner and I were slowly driving around (I think) Palo Alto on a Saturday admiring the houses and he suddenly asked “WHERE ARE ALL THE CHILDREN?”

I couldn’t unsee it. This pristine suburbia, optimized for families, perfect weather, but no kids to be seen. It seemed so weird to us who’d grown up mostly outdoors. In Ireland.
> I think they like exotic and unintuitive sounding stuff.

Exactly the opposite, nonlocality is by far the most exotic resolution here. It means losing existence and uniqueness of solutions to differential equations - i.e., causation.
The Code as Documentation crowd produce beautiful code, and I follow much of the practice, but while it is good at self-documenting what is happening, it's hard to get the why entirely into code without being obtuse. Especially when working around framework limitations. This becomes very important in the maintenance phase.

I can see you getProductCollection, I know what that does, but why do you do nothing with it? Oh it's because it needs to be loaded before presenting the cart, and there's a bug in the framework that fails to do so in this scenario.

Also business requirements can be reaaally asinine, a makeThisParticularButtonGreenSeeMeetingNotes20122023() would be pretty lame but that is often required information for a developer revisiting a feature and wondering if something was a bug or intended.
This 'lover boy' scam is a big industry in Japan, it's called host clubs.
> Ten years ago, everyone interested in military aircraft who was not trying to sell the F-35 told me that it was terrible

IIRC, the most serious criticism of the F-35 was mostly not that the fighter was terrible, but that the decision to pursue the project in the way it was was terrible, that the misguided attempt to try to save money by commonality among the radically different missions of the main versions instead made each variant more expensive to develop than it would be independently, compromised capability, and didn’t solve logistical problems better than separate projects would have.

(There was also criticism based on the cost arc of manned fighter development vs. alternative technologies and countermeasures against them that in terms of funding mix, the US should have been spending more on alternatives/countermeasures and less on manned fighters including the F-35, which was an even higher-level meta-criticism.)
This is a good point, and I'm not arguing with it, but I don't think the words "code cannot lie" are the right way to express it.

Code can deceive even if, definitionally, the code states what the computer will do. So code most certainly can lie.

[By analogy, you'd still feel lied to if someone told you something that is technically correct but very misleading: "(Me) It's going to rain tomorrow." → tomorrow comes → "(You) It isn't raining today!" → "(Me) It is raining, in Japan. I didn't say it would rain here."]

I suppose it depends on whether you're considering what the code communicates to the machine or what it communicates to a person.
> Try and write any complex SQL as a series of semantically meaningful CTEs.

Could you or anyone else on the post provide an example?
i’ve been working remotely for a decade and i’ve never been happier. i also suspect that the population being happier is no doubt bad for corporate profits.
It is a truth universally acknowledged that in any discussion regarding the US and social policy Australia simply does not exist.

The only viable comparisons permitted are that Socialism == Communisim == Stalinism and that if not rampant capitalism then obviously Cuba or Venezuela.
Yes. Not to bothered about the account sharing but it’s looking like it may add a bunch of friction to use Netflix away from your primary residence/device.

If the friction becomes to much, Netflix looses its value and illegal downloads look more appealing again.

When current budgets are tight I can’t see how Netflix wins with this as likely will push away users as it’s a non essential service with declining content quality as they’ve gone for quantity not quality now and Netflix isn’t the only streaming provider in town now.
> Why shift from a dedicated memory channel and chip to a shared one?

Cost, mostly; maybe pincount and routing at some level as well (I think current connectors have pins for ecc, but maybe this enables some pinsaving for ddr6 or the new ram connector from Dell?).

But also maybe performance? ECC ram usually doesn't come in high performance models, but with in-band, you can use whatever ram. Clearly, there is a performance penalty for in-band vs no ECC with the same ram, and there's almost certainly a penalty for in-band vs side-band at the same ram timings, but is there a benefit for in-band with faster ram vs side-band with conservative ram? Maybe? need approrpriate benchmarks.

If this has similar reporting to machine check exceptions that proper side-band ECC supports, this may be an easier path to get ECC on low end machines than hoping all the stars are aligned for ECC support and then paying a significant premium for the ram.

DDR5's on chip ECC probably increases reliability, but also means failures will be worse. You'll always have at least two bits flipped if bits are flipped on the chip, because single bit errors will be corrected. It's not clear what will happen with errors that are detectable but not correctable, since, AFAIK, there's no mechanism to report errors.
I think it's closer to 14%, no? 449 million out of 3166 million total.

How much does each of those ad-supported users cost each month? Those 295 million users account for as much revenue as 34 million premium users, but they probably cost a lot, not to mention that the ad sales and ad infrastructure isn't free either.
I just tried the op comment and got

> The classifier considers the text to be very unlikely AI-generated.
A break-even user is a low-risk opportunity to upsell in future and it’s the long term ability to starve your competitors of an audience. If Spotify cut-off ad-supported users today, another service would scoop them up which poses a risk to Spotify: what if the competitor discovers how to convert those free users to paid?

There’s complex dynamics at play when offering services to consumers that aren’t necessarily reflected in the numbers. For example, Netflix may believe they’ve reached a point where an advertisement-supported plan won’t cannibalise their higher value subscriptions and therefore now is the right time to do this when maybe it wasn’t right a few years ago.

Consumer behaviour is constantly changing, companies have to keep up with it (and even anticipate it) lest they fall out of favour.
Lmao, the never amount of times a page felt faster or more responsive than a page refresh. Oh joy, i clicked and nothing is happening and i get no progress notification. Really great.

The entire premise is absurd. What application spends more time on SSR than data fetch, or other? Exactly freaking zero that ive ever operated.
You keep retreading the same ground. Have you actually gone out and researched why so many people are telling you that SQL is declarative? Right now, it is reading as though you are being willfully ignorant of the entire field.

Worse than just ignoring the entire field. You are caught up in a strict taxonomy that just doesn't work. Cooking recipes are, amusingly, mixed. They are a declaration of all ingredients and supplies you will need, with an often hybrid list of instructions on how to mix them. Would I declare them as fully declarative? No, but nor would I declare that they are imperative only. That is a part.

And again, your definition of functional versus imperative versus declarative will get you in some amusing historical binds. With how strict you are trying to be, literally no programming language is declarative. Even haskel has do notation.

Please give some effort to understand why so many people are telling you you are wrong. You are not wrong, in that if you expand the concept of SQL to everything that is possible with the language today, there are concepts that are not declarative in it. You are sadly misguided in thinking that makes your point. Would be like my sneaking in the "script" tag to laugh at how HTML is not declarative. It is a markup language, not a programming one. And people have done a lot to add to it so that it can do more than it originally could. Often out of necessity to get stuff done.
These are great goals. You have a lucky kiddo.
I had to double check it wasn’t April 1st.

This is a good way to lose your best employees.
Happy people typically don’t spend as much money trying to drown their sorrows in consumer crap, food, and drugs.
No, but it is bad for some rent seeking players with loud voices.