skysight-inc/HackerNews huggingface dataset:
Acadia is broken up enough that, if you stay away from certain sections of the park loop road and Mt. Cadillac, it's pretty manageable. Though even the western parks are a bit like that. The Yosemite Valley is a mob scene for much of the year. But there are actually pretty large and very nice sections of the park that aren't nearly as bad.
> Landlords will figure out the "Legitimate use" legalese and paste it in each contract

I have no doubt that they will.

However, ultimately they will end up on this list https://www.enforcementtracker.com/ (or they were in the US and so it was irrelevant).

> and it is in the nature of data collection that mose abuse goes unnoticed.

Unnoticed by the average person maybe but people honestly think GDPR has had no _absolutely zero_ effect as well; doesn't make them correct.
UX Team of One: A flexible strategy for a new startup practice
Or fill one with slaves that make stuff for you without public controversy. The possibilities are endless
''The drive with the lowest AFR (0.28 percent) and at least 2.2 million drive days is Western Digital Corporation (WDC)'s 16TB WUH721816ALE6L4 (Backblaze has 14,098 units).''

''The model with the highest AFR (2.57 percent) and at least 2.2 million drive days is Seagate's 4TB ST4000DM000 (Backblaze had 18,070 units).''
Yeah that's what leads to situations like the Greek debt crisis [1].

You can't just rack up debt forever, and just assume that we'll pay it back later WITH INTEREST. You also can't just "cancel" debt; the bill eventually comes due.

[1] https://en.wikipedia.org/wiki/Greek_government-debt_crisis
Boost My School | Marketing Manager | Full-time | Remote, USA only

Are you a B2B marketing guru that would enjoy helping schools as part of a remote, impact-driven team?

Boost My School is hiring our first full-time Marketing Manager. The ideal candidate will be excited by the opportunity to grow Boost into an industry-leading brand by highlighting the success of our customers

See full job description for more details and how to apply: https://www.boostmyschool.com/careers#marketing-manager
It might be easier to delete all personal data indiscriminately than to process individual requests. A government might suggest that as a way to stay in compliance.
The model does not keep training every day on the current data. It would be nice if it could but no sign this actually happens. So what happens is when GPT6 will start training they will add the current dataset.
We have no reason not to assume that all reality in the universe has experience (consciousness). That's the whole point I've made there.

Your last sentence explains the second-to-last one: all we know is we have experience, therefore all we can assume about not-us is that it also has experience, because any other explanation would unduly add more complexity to the theory of consciousness in the universe. It's just Occam's razor.
I'm skeptical of legislators legislating in domains they're not knowledgeable in, while being advised by the players with the upper-hand in the field financially.
On the contrary, it _is_ 2FA: One factor is something you have (the phone) and the other is something you are (your biometrics). You need both to log in.

The difference here is you're allowing your phone's enclave to store the magic secret, instead of your human memory.

—If you're authenticating with a PIN instead of biometrics, it's still 2FA.
> Lisp is about a year younger than Fortran, which makes it the second oldest language still in use today

I disagree with this line since Lisp is not really a "language", but a family of them. If we consider Clojure and original Lisp to be the same language, we should also consider that to be true of Algol and Rust.
I’ve found the IKEA bulbs to be significantly worse than the Philips ones, so I would definitely say the price difference is warranted.

The IKEA bulbs aren’t as bright, get overwhelmed if you send a lot of commands quickly (so you can’t implement a dimmer for example, without the light jittering as it dims), and don’t have the “turn power on-and-off quickly to reset to full brightness” feature (though this is nice if that’s what you specifically want).
Wait, the LV underground Teslas have to be manually driven? An enclosed track like that is basically ideal for self driving, there is no reason they shouldn't be able to do it with their current tech.
I'm not american so I don't understand how a state like Colorado is so relatively cool/progressive these days based on its geographic location compared to the others (especially some of the least cool ones). Any cultural reason?
Expanded forced prison labor?
I agree but make them usable on mobile. Scrolling this article on a phone was an atrocious experience.
Sorry, I forgot the /s
Similar to legalized prostitution, this is where I often find myself at odds with my otherwise libertarian and personal freedom leaning beliefs. Should one be allowed to do with their body as they wish? In theory, yes, if it doesn't hurt others, but the reality is legalizing these things has a far greater capacity for harm at the hands of others who would exploit them.
As type specimen self makes less sense to me. In that sense it might make sense as the ur-language of it's own type (prototype-based OO languages), but it's too specific to be a specimen of the overall OO category.

I don't agree it made the concepts more OO in any sense. Self's changes feel far less significant than what Smalltalk brought to the table. That an object inherits it's structure and functionality from something that is itself an object is true of all Smalltalk derived languages I'm aware of, after all.
Also gives you that Hunt for the Red October feeling
Lexing separately is cleaner in that the lexer's only job is to produce tokens and then the parser's only job is to consume tokens and produce e.g. an AST. It also means that you can use that token stream for other things that don't require a full parse (e.g. for syntax highlighting). The disadvantage is that you're often doubling the allocations and increasing the memory footprint. I alternate between separate lexer, combined recursive descent parser and generated PEG parsers depending on what is more important: speed + maintainability, speed of execution or speed of development
Did Shannon introduce the term N-grams?
Rich city people like skiing.
If representatives in congress don't like debt maybe they should pass a balanced budget. The debt ceiling is political theater.
Another way to forcefully cancel a subscription is simply registering with a card to which you can manually add or recharge credit, the day that you do not put money in it (or remove from it), the subscription should be automatically cancelled as they can't debit that amount from you (yeah, it doesn't work if you're subscribed to several services. Or maybe it could if you meticulously add/remove credit the exact days that they charge you provided different days for each service, but that's just too much overhead).

If I recall correctly for example with Revolut it is even possible to generate virtual cards, which is great for security reasons as well.

For people that run their own mail servers no need to use any useful or real email addresses when signing up, simply use netflix@yourdomain.com, amazon@yourdomain.com, etc. Again you have 100% control over those email addresses and make sure that all trash/spam/undesired mail goes exactly where is supposed to go.
A lot of people in Colorado go outside on a regular basis to hike or ski or ride bikes.
ECB monetary policy was a huge factor in this.

When they started QE, the effectiveness was heavily limited by the small size of the securities market relative to the broader banking sector (this is why they did TRLTOs and things you didn't see elsewhere). So international borrowers started issuing in EUR realising that the ECB would buy their debt, and this has only accelerated now that US rates are rising (it has also led to massive growth in private credit and other extremely inadvisable products).

The problem with this is that it isn't possible for the EU to suddenly have US-style, open financial markets where savers get paid a fair amount. It undermines the system of pensions, undermines the heavy corporatism, it undermines the whole economic model of most of Europe (even countries like Italy that have larger financial markets, it is largely due to the needs of govt finance...their govt debt cannot be financed without extraction from domestic savers...this becomes impossible if they have options).
Rather than this law, I would start at banning social media accounts for under 16s.

Social media has arguably had an appalling effect on the mental being of teenage girls.

https://www.independent.co.uk/voices/metaverse-facebook-inst...
How is that not just K-complexity? A larger model is a larger interpreter. The entropy is just moving from the stream to the state machine.
Short answer: Some combination of efficiency, simplicity, and error messages.

Mostly efficiency. Lexer-specific code can be significantly faster on input with large tokens.
Yes, but other than techies most people find it reasonable.
The feature is the discounted price of the OS. See, MSFT wants to charge you about 3x the MSRP and gain recurring revenue.

Although they won't give normal users this option, if you wanted the non-spyware version of Windows, you would need to pay a subscription.
The split in lexing and parsing is indeed artificial and one often has to make use of states or even cases where the parsing is controlling the lexing. Try for example to parse an HTML file with embedded CSS and/or JavaScrips using lex(flex) and yacc(bison).

Recursive decent, where the parser asks the 'scanner' to accept a certain symbol at a certain location in the input stream, resolves most of these problems, such as for example the fact that in HTML the tags are case insensitive while JavaScript the keywords are case sensitive.

If you try to develop a parser that is user-friendly, but maybe not the most efficient (if you allow back-tracking) the whole problem of parsing become far less complicated. (There a good methods to counter performance problems due to back-tracking.)
Lexing should be strictly local and possible to do as a state machine that is reset after each token. So if something depends on the context, save it for the parser.
Now that Colorado has removed state preemption laws, what is stopping ISPs from lobbying and preempting state level laws at the local level across the whole state.
> “There’s going to be a generation of voters that can’t get anything they want, because all the money has been spoken for.”

Interesting to hear an expert take from someone with decades of experience show some empathy to what likely will be GenZ or Gen Alpha. I've been saying for a long time now that govt debt is a very problematic tool because it allows today's leaders to create obligations for folks who didn't vote for them (likely couldnt vote at all). Even in perfect intentions it's not consensual to burden future generations with debts they had no voice in choosing.
> But it still doesn't matter. It has never mattered.

Following this logic, why pay taxes at all? If the amout of debt the USG taking on is irrelevant and a "scam," then why not just set tax rates to 0%?
JN is an escape hatch, similar to those built into programming tools.
You really cannot and should not take away the ability of people to step back from a situation and realize the the law, when applied, leads to a perverse outcome that is truly abhorrent. The jury is how you factor in a "gut check" into your system.

To be sure, this can fail. You get a bunch of jurors who are ignorant or evil in a coherent way, who decide to ignore the law and effectively lynch a man because he's black or back up the school administrator who wants to teach creationism or Jewish space lasers or whatever. Personally, I think that's an acceptable risk, in part because if you take the application of the law away from sentimental flawed rational animals you have to give it to someone else - someone (or something) with power and sitting in the seat of authority. In a sense one way to characterize democracy is as a constant struggle between jury (electorate) and judge (political leader). The way the jury system is supposed to work, the fact it was written into the Constitution, is indeed very important and I'm glad for this sub-thread is talking about it.
It could potentially be argued that the prevalence of divorce is what negatively affects the largest number of children.

Non-fact-based opinion:
Stable relationships create stable children, and stable children are less prone to predators.
Tracks are expensive. Railcars are very expensive.
TikTok is currently being considered for a total ban in the US isn’t it? And it’s banned on US government devices? Not the greatest example to use for your point.
two things about splitting into phases:

1. history (scanner, lexer, parser all would not fit on one tape/cassette/disk back then)

2. performance (each component can benefit from specialized optimization techniques without affecting the other)
We've been getting WISP rollouts and it's causing comcast to offer some seriously good deals. I still prefer my indie ISP. $40/mo 100/100 guaranteed, up to gigabit symmetric.
I'm sure they can be programmed to flop.
This article isn't even accounting for all the UAP information that has come out in the last 2 years.
The small size of the The Boring Company's tunnels seems perfect for bicycles.

https://www.cnn.com/travel/article/worlds-longest-cycling-tu...
They are enumerated here: https://new.nsf.gov/news/nsf-announces-seven-new-national-ar...
Remove it from the training set and train again. Don't do it per data erasure request, batch them and run it, say, every 30 days.
What is the viable alternative to land ownership?

The Tragedy of The Commons is a well known and frequently repeated experiment in many areas of life.

https://en.wikipedia.org/wiki/Tragedy_of_the_commons
Heavy marijuana use increases schizophrenia in men, study finds
Feigning ignorance is another common form of pedantry.
the Swiss are moving ahead with a similar project for underground good transport vehicles.

https://www.google.com/amp/s/spectrum.ieee.org/amp/cargo-sou...
The internet is vast and growing ever more vast.

It's getting a "skinny waist," a la TCP.
The last time I cancelled Prime from Ireland, I still encountered dark patterns. Lots of attempts to get you to reconsider, buttons being labeled "Lose my Prime Benefits" instead of "Cancel", cancellation links being a lighter colour and not clearly identifiable as buttons that kind of thing.
When you get into a situation where the approach you take causes people to start playing whack-a-mole to patch issues that arise from said approach, it's a sign that it may not be a good approach after all.

Your IDE will do type checking as well. Yes, the lexer stage will parse all identifiers into 'ID', but to provide a contrived counter-example, what if I do want to allow 'pi' to be assigned based on something that can only be processed in a later stage (perhaps an annotation, or a result of compile time function evaluation, etc). It will push the logic of handling 'ID' to later stages anyway. Now you're handling IDs in at least 2 places - that's strictly worse than the status quo.

Part of our jobs is to be able to reason about trade-offs when making decisions. Pointing out that the lexer has a limitation does not necessarily justify removing that limitation for an edge case because it might be due to that limitation that it can be kept simple for the general case.

Adding complexity to the lexer without simplifying the later stages is a net negative in my opinion, which would make this trade-off not worth it.

Is it an interesting approach? Sure. Is it worth it? Maybe in some very specific use cases, but it doesn't seem like a convincing argument to me to combine the lexing and parsing phases.
I'm not sure that explains the difference between Colorado and Wyoming.
- violation of guest policies (having too many or staying too long)

- if you hook up a decibel meter, being too loud

- loitering

- allowing someone to tailgate

etc.
Lexing translates raw characters into non-semantic tokens. Punctuation is a good way to demonstrate what I mean by non-semantic. Take Rust, which uses `{` for both blocks and closure literal expressions; and uses `<` for generic parameter/argument wrappers, and also a binary operator. While lexing, you don't try to determine whether `{` is opening a closure or a block, or whether `<` is a binary operator. You just turn them into the tokens `LeftCurlyBrace` and `LeftAngleBracket`. It's the parser's responsibility to take those tokens and their neighbors and figure out what they're being used for.

The benefit is that this keeps each stage much simpler: lexing doesn't have to do much if any lookaround, and parsing mostly doesn't have to do anything character-wise.
> Let's reinvent the subway but call it an "electric van" so that Americans don't feel squeamish.

This is comedy gold.
Self-filibuster?
> IMO, they're just trying to get through the things they want into legislation

This is crowd-pleaser legislation; they're hoping it's a vote-winner. They think they have a chance in the next GE.

I'm inclined to agree; I can't vote for Starmer's party, so unless something changes, I won't be voting.
There's a decades old definition for what today's "A.I." is:
https://en.wikipedia.org/wiki/Expert_system

But apparently buzzwords are important for funding, or something.. There are toasters on Amazon boasting AI capabilities, the acronym has lost all credibility.
There is a case coming up at the Supreme Court that might rein in regulatory agencies and push stuff back to congress
Subeditors have been writing headlines for engagement since you had a crank a handle to print a newspaper.
Every comment from this account is defending or advocating for Meta or one of its products. Don't drink the Kool-aid, folks!
I took a look at the PDF. It is a fair take on a pitch deck, but the underlying business must exist and be demonstrable. In other words, if it’s just a concept, you won’t get traction.

Here’s my input…

I think it’s very important to note here that investors generally use the following criteria roughly in order of priority when deciding how to invest:

1. Founders-experience, expertise, boldness, commmunication skills, trustworthiness, life balance, etc.

2. Market size-is the market big enough to support annual sales north of $10MM in 3 years? Is there room to compete?

3. Go to Market-is the path to the market, including product development cost and schedule, within the budget of the amount of money likely to be raised (or supported by non-dilutive contracts)? How do you know? Where is the analysis?

4. Uniqueness/Disruption/Timing and Value-is the technology and product sufficiently unique to get interest from new customers at a price they consider to be more than fair? Is it the right TIME for this product? How do you know?

5. Financials-beyond use of funds, what are the projected cash flow and income statements per the schedule for years 1 through 3? No revenue is usually a tough sell, so this needs to look really solid. How do you know?

6. Customer Interest-you need to have actual customer (or potential customer) feedback from beta tests, demonstrations, interviews, etc. Not just a few of these, but more like 25-30 of these.

7. Everything else…
Can someone please explain?
The title of this post stood out to me because it's a fairly niche topic that I've been meaning to write a 'rant' post about myself. I think in a very 'pure' parsing theory sense, there is no real advantage to separating the lexer and the parser. I claim that any counter-argument is due to the limitations of individual software tools, and their inability to let up specify the grammar that we actually want.

If I recall correctly, the original historical reason for separating them was due to memory limitations on early mainframe computers. Actual source code would be fed into the 'lexer' and a stream of 'tokens' would come out the other end and then be saved to a file, which would then be fed into the next stage.

Having said this, you can ask "In practice, is there currently an advantage to separating the lexer and the parser with the tools we use now?" The answer is 'yes', but I claim that this is just a limitation of the tools we have available to us today. Tokens are usually described using a simple regular expression, whereas the parsing rules are 'context free', so worst-case complexity of parsing the two is not the same. If you pull tokens into the parser and just parse them as naive 'single-character parser items', then you end up doing more work than you would have otherwise since your parser is going to try all kinds of unlikely and impossible chopped up token combinations. The other big issue is memory savings. Turning every token into a (small) parse tree is going to increase memory usage 10-20x (depending on the length of your tokens).

Personally, I think there is a substantial need for more advanced ways of describing language grammars. The ideal model would be to have various kinds of annotations or modifiers that you could attach to grammar rules, and then the parser generator would do all sorts optimizations based on the constraints that these annotations imply. Technically, we already do this. It's called putting the lexer in one file, and the parser in another file. There is no good reason why we can't specify both using a more unified grammar model and let the parser generator figure out what to do about each rule to be as efficient as possible.

The computer science theory behind grammars seems to have peaked in the 1980s, and there doesn't seem to have been many new innovations that have made it into daily programming life since then.
If I understand the situation correctly, the law effectively just imposed a meaningless formality because all it took was a local ballot measure to override it, and as a practical matter it would also take at least one ballot measure to authorize the bonds/taxes to fund a network, so it just meant that voters needed to approve two ballot measures instead of one.
Tangential to this great post, I am reminded of the need to upgrade my lighting.

For anyone that missed the recent rabbithole of commentary on LED quality last month:

https://news.ycombinator.com/item?id=35371750 (35 days ago - 942 comments)
I'd love it if you could ask technical questions on the discord channel, as that's more scalable for us. Some quick answers:

1) We're likely to change the reference syntax to inout: https://github.com/modularml/mojo/issues/7

2) they're the same thing. Consume is the word we're currently using for the operator, owned is the argument convention. We may need to iterate on terminology a bit more.

3) Because it composes properly with chained expressions: `x.foo().bar().baz^.do_thing()` vs something like `(move x.foo().bar().baz).do_thing()`
That is a good point. We have to take wins when we get them. Getting the oligarchy to fight each other to our benefit is a nice turn of the tables. We should keep our eye on there competition as well though. Meta's whataboutism referencing tiktok wasn't baseless, it just isn't a valid excuse.
When media is sold for more money than you make in a month, or is otherwise financially out-of-reach, piracy is ethical (they would have never gotten your sale anyway)

When media is no longer available for sale or pulled from the market, piracy is ethical (there is literally no way to pay the creators)

When media you had legit access to is now unavailable because your account got stolen or you are otherwise locked out of some required online service, piracy is ethical (they won't do business with you)

When media requires something that was stolen from you, lost, or otherwise destroyed, piracy is ethical (you already paid for it)

When media uses DRM, piracy is ethical (doctrine of first sale stipulates you cannot control something after you have sold it, and one should not recognize any "license" for which have custody of the physical bits)