skysight-inc/HackerNews huggingface dataset:
Most Cryptocurrencies do NOT fulfil the definition of a security because there is no underlying "thing". This is why shares (with a company underlying them) are and bonds (with debt and debtors under them) are securities (that and the fact they can be traded) but currencies are NOT. Obviously there are exceptions to that like tokenised stocks. This is also why I would not consider most crypto an investment: there is no source for a reasonable expectation of a return.

In the UK, we just designate certain markets as "regulated" (stocks for instance) and others as not (eg FX). That would avoid this whole nonsense where the SEC etc have to argue that some things ARE securities and others are NOT (if bitcoin is a security then stamps definitely are, do the SEC want to regulate stamps? Or Baseball cards or cars, the examples are pretty endless...).

Watching all of this makes me think regulators either being disingenuous or dumb. I doubt it's the latter. So is this someone just grabbing power for its own sake ("I can get more salary and a better office if we get to regulate crypto)? Or maybe trying to get media coverage to up their personal brand for a political career? Either way, if congress wants the SEC to do this, they should pass such a law, and if they haven't then the SEC should be careful what it sticks it's nose into not least because regulating all of Crypto would be exceedingly difficult and error prone.
And that «pseudointellectual BS» would be mine? If so, is not that contradictory with your statement that being «very well-read» gave you abilities for discrimination?

(Note: if the above is correct, and they are incomplete, then it's duly to roll the sleeves again, and be back to the "discrimination builders". Like for all of us.)

I am not sure about that «trying to signal»: it seems as if you interpret that somebody uses books to "show off". That would be completely nonfactual. They are there for you, why should one use them to display - that would be strongly inconsistent with their nature.

Now the core point:

**

books are explicitly the concretion of an effort towards development

**

as such, they are symbol and object "incarnating" something very high.

I do not understand the expression «Get your head out of your ass», but I consider it a friendly encouragement, for which I am sincerely grateful. To actually meet in communication, we would probably need more exchange though - I think we have probably not understood each other.
> At least acknowledge the difference between ICO funds, NFTs, native tokens, inflationary or deflationary assets, liquidity pools, slush funds with voting and governance attached.

They don't want to distinguish between any of that and instead want to blanket all of them and say that they are all the same. Not all NFTs are JPEGs and there is an obvious difference between a 'coin' vs a 'token' where those blockchains which allow tokens, you will see them have ICO launches since 2016.

> Even getting some nuance on the different ways in which one thinks different crypto assets are a scam would be nice. But here I see no engagement or interest in the particular assets in question or the details of the story. Why?

I think the right approach is to wait for the Ripple vs SEC case which will not only determine whether if XRP (Ripple's blockchain coin) is a security or not, but the wider implications on other coins and tokens. But as for ICOs in general, the SEC has already cracked down on unregistered ICOs in 2018, making them illegal in the US.

Overall I don't think you will get a rational response on this site about anything mentioning crypto. Instead, the typical response you will get on HN is always to the extreme: 'All of crypto is scam', 'Ban it all, ban everything crypto, all of it', 'web3 should die in a fire'.

It is indeed the same absolutist nonsense that doesn't add any new arguments other than spreading regurgitated garbage that is recycled from other anti-crypto supporters and repeated here.
While impressive, this misses the point. The Moana scene is a test scene for /renderers/.

It is not meant to be used inside a DCC app, as-is.

If you import data of this complexity into a DCC app your workflow is broken/you are doing something wrong.

That said – I think it's very cool if you can import such heavy geometry and your DCC app doesn't crash.
But in 15 years of working in VFX I never dealt with heavy data inside a DCC directly. Indirectly yes, through proxies.

The three most interesting metrics for this scene are, if you're a renderer author (sorted by importance during lookdev/lighting):

1. Time to first pixel (is it seconds or hours?).

2. Time to completion (does it take days/hours/minutes?).

3. Memory footprint (does it 'fit' or does it go into swap?).

Two more are: subdivs and PTex.

I.e. can the renderer do true subdivision surfaces (vs just subdividing the geometry n-times leading to silhouette artifacts under certain viewing conditions)?

And: can the renderer ingest PTex textures or do you have to create UVs somehow and convert all the textures into UV-based ones before you can use the original Disney dataset?
1950 did not even had peer review. Peer review as we know it started in 1970.
There's LineageOS. Not sure it is worth the effort to switch just for this though.

Which is also the solution for "OS gorilla". Use Linux. You have a vibrant ecosystem of distros, they work (as much as any OS), and you are free to mix and match. No need to stick to OS that changes under your feet with no recourse.
I still have n9, n900 and Jolla 1
I feel like for 1.4 million USD a year I could solve that problem for them.
Not just that, it's also expectations. Traffic runs on a stack not only of rules, but also of cultural conventions. And both rules and conventions exist not only defining the dos and don'ts for drivers but also defining those of traffic engineers.

When we drive in a different country we know that the driving rules are slightly different. We suspect that the conventions for driving are not quite the same.
But the differences in rules and conventions of road design are mostly invisible. We may notice the most glaring differences like preferring roundabouts vs preferring crossings, but the large majority of those design principle differences, they are so close to invisible that we expect our expectations to still work. But they don't. Everything just feels subtly off, and sometimes there's a large difference standing out and we just declare that badly planned. Even when it's in fact perfectly in line with local expectationsand usage patterns, and works just fine (except for the confused foreigner). We notice a few standout differences and then blame every bit of traffic badness we encounter nonetheless on the few differences we consciously notice. The parts that work well are usually completely invisible, because traffic, in our perception, only exists when it's bad.

Rules/conventions on the design side exist for and can differ in just about every aspect, down to draining angle of road surface (do you drain symmetrically or to one side? Do you switch to draining to the inside in a curve? What about softer curves, sharper curves? A consistent threshold is very valuable, but if one country has a different consistent threshold than the other it feels "wrong" to everybody cross-driving even if no side is objectively better). Or the general shape of curves, some places have strict rules for keeping the second derivative of direction as flat as possible, with few, definitive jumps, others prefer a gentleness above all approach.
I live in Phoenix. Bring it.
> - lightweight and thin

Thin is a _problem_! Thin means:

1. The design of everything needs to be warped to fit in - less opportunities for modularization and more contortion needed for disassembly.

2. Bad keyboard with almost no key travel

> They started going downhill after that

I would say the X220 era is where things started going downhill. Although some might argue that it was even earlier.
To be fair most deaths are the fault the the street design that prioritize driver comfort over everything else
St Charles. This brings back memories. I fly in at like 9pm and there is nothing open to eat, at all. Only one slice of leftover pizza at the "social centre", and it did taste like cardboard.
Reading this, I can totally see why I fell in love with Golang. The language is so dead simple that it's generally a pleasure to read any codebase, and very fast to learn/write.

That being said I write mostly in Rust these days and really like it too. There's definitely a number of issues in Golang that I wish they would address (sum types for example)
I wonder if Swift's AsyncAwait could be used in such a way.
That kind of thing is a common extension to ropes, because it makes them indexable containers like arrays, but it is not inherent to the definition of ropes. I don't think it's mentioned in the original Cedar rope paper.
I recently learned how to solder. It takes like 20 minutes (and a small investment of money) and is definitely worth it. No more "oh I don't know how to solder, I can't do that". I've since built a bunch of electronic kits, including stuff that is only available in kit form. It's been pretty fun.

Recommend the Pinecil!
There is a perverse incentive when the client has a retainer to bill hours and makes excuses to line their pockets. Why tolerate this behavior? The customer is always right, force them to stick to the contract or break away and take them to court if they are working on things outside of your contract and billing you.
Maybe, maybe not. Technologies that are 'good enough' just stick around forever instead of being replaced by something entirely else. Wheels are still round, we still print words on paper, we still use glass lenses when eyesight starts to fail, rifles don't look fundamentally different from when they first appeared, etc etc...
I don’t really see what you mean, perhaps you tried Rust many years ago?

Because for stack-allocation there is zero lifetime annotations, it just works with as high-level code as you would get from a managed language. Rust’s complexity happens when you want to introduce non-tree-like memory patterns.
Soho House is just silly now, I literally know of law firms handing memberships out as an employment perk.

So much for being a cool place for creative folks, now they just let everybody in.

Also, at least in London the clubs simply suck. 0 atmosphere, even Annabel’s with it’s older crowd and their sugar babes is much more fun.
Yes, but I think you missed the point of the parent comment.

> enabling developers to easily assign their own allocators

Through a combination of Zig's convention to pass around allocators instead of using a global allocator, the allocator interface's ability to return errors, and the Zig language forcing you to handle all errors (unless you explicitly discard them), a lot of Zig code is written with allocation failure in mind.

This means that you can seamlessly pass a custom allocator, say a bump allocator backed by a fixed buffer, to a function in some third-party library and still handle the case where the buffer runs out of space.
I kind of disagree. I like the gamer nexus reviews, but the constant stream of perpetually angry/ranting videos also gets tiring at some point. Like yeah, controversies and angry call outs are fun but what's the point?

I prefer the ltt approach here. They went pretty hard on Intel on their original Arc video a few weeks ago, but the fact that they are known for not burning bridges made it worthwhile for Intel to respond and showcase the improvements they have made since. As I said in another comment, they wouldn't have bothered if linus could've been just paid to update his review to make intel look better. But I also don't think Linus would have had that type of influence (enough for a corporation like Intel to engage with his complaints directly ) if he just kept burning bridges instead of keeping channels open.

(Gamer nexus is far far from the worst in that regard, and they too had a visit from intel engineers. But I still think the LTT approach is just different, but I dont think that means they are just corporate shills.)
ChromeOS is everywhere in public schools in Denmark. I doubt that Denmark and the Netherlands are the only two EU countryes that use them.

However, ChromeBooks will also be banned i Danish schools when the new school year starts in August. The Danish Personal Data Authority (Datatilsynet) have just told the schools that they cannot use them after the summer holidays, for more or less the same reasons and their Dutch colleagues.

The problem then becomes: Which laptops can you get in large enough numbers, at a low enough price, within three to four weeks?
I'll check it out. Thanks for the suggestion.
For the most part. I think most of the usage was to allow more dynamic ‘objects’ and queries on them to be used in a low friction way without worrying about generational validity checks or null checks when reading data from those objects. It a lot like implementing a deterministic GC for a small set of memory objects.
I this attitude a lot, especially from Americans. A 'well if you change this to help A, this other thing B will get worse'. All while the US is at the bottom of list for both A and B.
> Not to mention that Amazon should have known that I already had novel 8 on my Kindle.

Amazon doesn't seem to understand many things surrounding the Kindle. For example, it calculates the progress reading through a book by the last page I looked at. That means if I finished a book and jumped to the introduction it'll now be convinced I only read 1% of the book. This is so dumb, and I don't know why they even do it that way - the Kindle hardware should easily be capable of precisely keeping track of what pages I looked at.
IMHO if C could solve all the same problems as assembly, it would need to be down on the assembly language level - which it isn't, C is clearly a high level language, it's much closer to any other programming language than any assembly dialect (maybe with the exception of Forth-like languages).

In general, the higher level the language, the more flexibility you need to give up (but that's ok for many solutions).
https://nitter.net/mcfunley/status/1550219636464967680

I hate it when you don't realise the thread ends and twitter shows you a full sized login banner where pressing back doesn't bring you back to the thread but instead goes back to previous website.
Interested that as well, especially the old school lisp to this new Ai.
Rust is getting custom/local allocators as well.
Canada policy sometimes follows in UK footsteps. There's a relevant table on page 7 of this 2020 UK document, https://www.repository.cam.ac.uk/bitstream/handle/1810/29941...
I'll check it out. thx...
Neopets data breach exposes personal data of 69M members
Is this an example of the Market for Lemons? If I hire a developer I have a pretty good idea what to look for (and to a lesser degree, a designer, as I have worked with enough designers to know how the good ones work). But I would have no idea what makes for a good accountant or corporate lawyer or plumber, so would need to depend on referrals and a certain amount of blind trust.
DeepMind: The Quest to Solve Intelligence
Absolutely this and you can take them to small claims court for breach of contract.
Honestly this reads like the journalists are doing the opposite.
Wow, is this an AI written promo piece for the Jerusalem Post or have they spoofed it?
Nearly 300 comments and no one said

Rainbow Tables.

Sure, they not used anymore and are not particularly useful nowadays, but I find the idea behind them very beautiful.
Thanks for this, the critiques are useful enough at layman level and say just about what I expected. I do appreciate the spirit of the article itself opening the solution space to additional therapies than SSRI medication, which may seem obvious but I feel is important to articulate to the general public.
Not particularly innovative, but extremely useful: HDRHistograms let you very efficiently create, combine and query empirical probability distributions.

If I'm doing anything with random or random-looking variation, I prefer to store the full distribution in a HDRHistogram rather than just the last value, last few values, mean value, or whatever. Opens up so many possibilities for analysis later down the road.
A bit off topic but why exactly are you disliking Drone?
Erm, Go channels were a pretty big deal in the beginning, as well as the idea of creating a 'better C' (instead of a 'better C++').
Yahoo.

(Yes, I'm showing my age here, I know...)
If that's so, why is the luggage weight allowance applied cumulatively across multiple bags for one passenger? And why is it different between airlines and between ticket classes?
Indeed, but it took a while for me to appreciate Tries.

Originally, i thought "nice idea", but I rarely ever encountered a problem where I really needed a prefix tree.

But while reading into HAMT and Clojure's datastructure implementations, it dawned on me that prefix trees aren't only useful for strings (or arbitrary byte sequences): Hashes in a dictionary, for example, are sequences of bits, too. And the design of a HAMT is exactly such that it doesn't concern itself with bytes but any blocks of N bits (determined by the branching factor; i.e. a factor of 32 implies 6-bit-blocks). And if you know the length of each sequence (hash), you know the maximum Trie depth, which also works for you, not against you.

That was rather eye opening for me at the time.
Apprenticeship Patterns(https://www.programmingbooks.dev/#apprenticeship-patterns) and Pragmatic Thinking and Learning(https://www.programmingbooks.dev/#pragmatic-thinking-and-lea...) are two books I wished I read early in my career. I read them many years into my career and still feel they had a big impact on me but I believe they would have had a bigger impact if I read them earlier, within the first year of me being a professional developer.
> I've noticed that I was the most creatively productive when I had a longer planning horizon in front of me.

Assuming that this is generally the case (which I do), and given that longer planning horizons have become rare in academia over the past decades, the logical implication does seem to be that productivity in science decreases.

How to measure and how to value academic productivity is another interesting question.
My wife? My friends? Honestly though I don't care who is at my funeral, I'll be dead
No knowledge. But we’re told that translation from Arabic is where https://en.m.wikipedia.org/wiki/Italian_Renaissance is started. Not detail in wiki though.

“ The Italian trade routes that covered the Mediterranean and beyond were also major conduits of culture and knowledge. The recovery of lost Greek classics brought to Italy by refugee Byzantine scholars who migrated during and following the Ottoman conquest of the Byzantine Empire in the 15th century were important in sparking the new linguistic studies of the Renaissance, in newly created academies in Florence and Venice. Humanist scholars searched monastic libraries for ancient manuscripts and recovered Tacitus and other Latin authors. The rediscovery of Vitruvius meant that the architectural principles of Antiquity could be observed once more, and Renaissance artists were encouraged, in the …”
Yup, so since it kills some people and is a really terrible illness for others, those who like you who had it easy need to be a little more considerate in how you talk about it. Just because it was "like a cold" to you doesn't mean we shouldn't care about it.

I am double vaccinated (Astra-Zenaca) and have had a single booster (Moderna).

I was on the floor in the foetal position at my worst, while my spouse just had a cough and very bad headaches.
I invite you to think about the problem for a while, and try to think of a way to implement a performant deque on top of a resize-able array. I promise you it's possible.
Generational references are best seen as an alternative to RC that makes different tradeoffs. They add overhead to reads/writes thru the managed reference, as opposed to the overhead for changes in ownership you see wrt. RC/ARC in something like Rust. (Note that other languages like C++ or Swift cannot cleanly separate ownership changes to the same extent as Rust, so their overhead is ultimately a lot higher. Especially Swift, with its ARC-for-everything approach.) They look like they might be good complementary approaches.
Horrible for todays hardware but i also came to say this.
The problem is not “a length of a vector”, Rust is not that fine grained. As far as Rust is concerned, what can happen is that you acquire an immutable reference to an object while there’s a mutable (unique) reference outstanding, you can invalidate the immutable reference via the mutable one, and thus have a dangling reference, which is UB.

Hell, even here one could imagine two scoped threads (so they can work with references), one thread keeps modifying the vector, and on some ISAs the other might get torn values for the length, or possibly worse (I don’t know if worse is an option but I wouldn’t be surprised).
Interesting that it sounds like that tweeter thinks that Coinbase wants the SEC to go after this case. In reality Coinbase is upset that the SEC went after this (but fine that the DOJ went after it):

https://blog.coinbase.com/coinbase-does-not-list-securities-...
Link cut trees. They can be used to query information about paths in a forest, while also allowing you to add and remove edges in the forest.

For example, you could use them to store the minimum spanning tree of a graph, while supporting updates if edges are added to the graph.

They can also be used to speed up max flow algorithms by finding the augmenting path in logarithmic time.
With the motto: how to write an article without saying anything.
And once your job becomes non-interesting, what do you do? Quit? How many times?

I expect some excitement from my work but in the end it is just work. I work 8 hours and they pay me for that. I think having that personal attachment to your work and expecting more from it leads to early burn out when things are not going great
>One other change to the website that I feel like is well-supported by this point was changing how we present our products. We used to show four products in our catalog, but in November, we simplified the website to show only our flagship product, and it was almost an overnight doubling of sales that's persisted ever since:

This is much more correspondent to the "mental model" I have of the majority of your customers, they want/need a Tinypilot , and they get a Tinypilot (as fast and as directly as possible), no matter how the site looks.

Maybe there is a coincidence of some kind, something else that increased the visibility of the site or the knowledge of the device existing at the same time of the site redesign.
You can efficiently maintain count/max/sum/hash/etc. for each component. It's occasionally useful.
Do you have any links about that?

I did a quick search but didn't find anything substantial.
Theengs/OpenMQTTGateway: MQTT Gateway for ESP8266, ESP32 or Arduino
I was wondering why I had never heard of this advice, and it's because I started lifting in a powerlifting focused circle so the advice was always hips back, weight on the heel. We also only go past parallel in depth, we can get impressively deep but you don't tend to see that transitional moment where the body shape changes and weight shifts to get ATG. There is also no way I would want to be in that transitional phase with the amount of weight powerlifting asks of you, I think you'd be pretty compromised with the low bar squat.

I have never had trouble with my knees using powerlifting technique. My first injury was actually when I tried to transition into a general strength focus and started doing highbar squats, it was probably just my lack of experience with highbar and an overconfidence from my previous lifting lowbar, but I tweaked my back. It took over a year to recover fully.