skysight-inc/HackerNews huggingface dataset:
It's not surprising that HTMX didn't allow you to do that because that's pretty explicitly not what it wants to be. HTMX is all about sending HTML over the wire, not JSON. If your HTML/JSON is gzipped, it shouldn't be significantly different in terms of bandwidth. Plus, you're not bundling nearly as much javascript with your site compared to a heavy client side framework, not to mention savings from avoiding processing more than just the DOM update on the client.
Use Pandora in discovery mode, and add variety to the station with multiple artists. You'll probably find something new that you like.
Hi, professional C++ developer here, I find this post casually and, for curiosity, I watched the video. The example used by the guy is wrong beyond recovery and I'm about to detail why after the premise that, yes, exception are slow:

1. exceptions have that name because are intended to handle event out of normal , error and not to returns value or information to the caller. No skilled C++ developer will write functions like those, never !

2. In that kind of function exception are useless, in fact that should be write like this, with exception disabled:

int calc(int a, int b) noexcept {

if(... omissis ...) return 1;
return 0;

}

3. In case the function had some more complex errors, the correct form for the use of exceptions should be:

int calc(int a, int b) {

try{

// More complex logic here

if(... omissis ...) return 1;
return 0;

} catch(myexcept& ex){
// do something
// possibly other catch for different except here
} catch(...){
// do something
}

}

So, not to return information but for error handling.

3. From a skilled developer , from a financial company, I expected a real life example , with correct exception use and a real case in which their presence can slow down a critical section of a program. That could be an interesting lesson;

4. Moreover, the examples are particularly bad because could induce people to think that in other contexts, where performance are not so important, the use of the exceptions in that way is justifiable ! I guess that could be a reason the article was downvoted.

5. I hate "dogma driven programming", IMHO to demonise whole class of features of a language without critical sense is wrong: yes most application has critical sections that are performance sensitive but, also frequently, large portions of them are not. So why make programmer's life miserable banning without think features like exceptions or polymorphism "because is written"? Moreover, if some little parts is justified that are written even in Assembly, maybe large chunks could be written in Go or Python without influence on the general performance of the system.
Scientists strengthen concrete by 30 percent with used coffee grounds
Very impressive! Since it wasn't immediately clear, the author is based in Cambridge, UK.
not really

marbles = (BlackMarble() for _ in range(random.randint(0, 10)))
all(isinstance(m, BlackMarble) for m in marbles)

Surely should always be true
Is there a monetary advantage filing for IPO in the current downturn? I know the owners will get less money per share but is there a long term advantage?
Apple breaks enough things by accident that I find it easier to believe that than than they deliberately targeted this replacement screen and found a way to make their hardware and software still work well for existing users, and break just this third-party screen.
I dont think you will whilst inflammation is seen as something bad. If you look at what causes inflammation, like zinc, inflammation not only destroys the pathogen, but also destroys surrounding host "healthy" tissue.

Now if elevated levels of zinc cause this inflammation, the new tissue that replaces the destroyed host healthy tissue will have elevated levels of zinc in the cells compared to the previously destroyed "healthy" tissue.

Ergo, is this the body's way of using minerals to increase the anti bacterial nature of the cells in that part of the body, and why all inflammation should not be seen as a default bad thing?
Also if anyone has tips on how to get the contents of the hrad drive out if you can't remember the password?
> At least in the 90's, the People's Liberation Army was the biggest buyer of squirrel fur; I was told they were used to dr hoods on winter jackets. That may have been as case of get the pelts no matter what.

If Mao hadn't gone on his retarded crusade against squirrels, they wouldn't have had to do that lol.
Bowerick Wowbagger?
Returning partial HTML from endpoints is the whole point of htmx. If your endpoint returns json and you’re trying to convert that to HTML to use with htmx, don’t bother - just use another “traditional” Js framework.

I highly recommend the “building hypermedia systems” book (free at https://hypermedia.systems/) so you can understand the HTML/ hypermedia architecture of which htmx is a key component and how it’s meant to be used.
Or we could stop building throwaway things. Sure it won't reduce mining to zero, but when a significant fraction of what we mine is ending up in landfills after just a few years, there sure is margin of improvement.
The citizenship doesn't really matter, b/c Russia may want to kill own citizens too (ex., if they don't support Putin).
It's a really fun place to visit with vibrant city-life and very friendly people.

Just a about all my Chinese American colleagues love going to China for vacations and quite a few plan to retire there due to the lower cost of living.
> My friends: well, I am usually the person that is supporting them when they are in crisis.

It's time to call that in. Get your friends together and tell them that this time you need their help. Don't face this alone.

And judging from your resume - and I mean this with all kindness - you may need some mental health support. I don't know how it works where you are, but are there public or charitable options for this? Please: try to find some help. I suspect you may need this before you can find solutions to your more tangible problems.

I wish you well.
They will lose some of their best people doing that.
Not sure how much you details you can provide, but I know RH products use Terraform under the covers for a few things (like in OpenShift). Are you removing this functionality because it's no longer FOSS or fears around the BSL verbiage?
You might enjoy Angel's Petrochemical. It's a bit closer and I felt very accomplished when I made a lot of plastic.
I liked Julia Evans' take on this: https://jvns.ca/blog/2023/02/16/writing-javascript-without-a...

"""
My goal is that if I have a site that I made 3 or 5 years ago, I’d like to be able to, in 20 minutes:

- get the source from github on a new computer

- make some changes

- put it on the internet
"""

Front-end build scripts make sense for projects that are constantly developed by a team that is actively ready to incrementally fix any problems that come up.

For sites that only get maintained every year or so (and I have plenty of those myself) my experience is that they often cause more problems than they solve.

I also found that I started really enjoying JavaScript development again once I gave myself permission to ignore the npm/webpack/etc script world entirely and just write regular code that runs in browsers!
The paper "Interpreting the retinal neural code for natural scenes: From computations to neurons" is available in the journal Neuron at:

https://www.sciencedirect.com/science/article/pii/S089662732...
I like hot module reloads more than F5 since it preserves the state of the page. I don't use Angular though, but with Vite + React it's extremely quick.
And it also has an update nearing the end of development est 2024) - Shapez 2 [0] , rebuild in 3D (with 3d belt layers same as Dyson has) with new features

[0] https://store.steampowered.com/app/2162800/shapez_2/
why do you need hot water?
Some Tips for Scientific Writing
> In other words, there is a subset of distributed problems that Distributed Erlang solves very well out of the box: homogeneous systems working on ephemeral data. And some of the scenarios above are very common.

Speaking of which, I'm looking forward to using Broadway [1] in a new project here in my company. Here, people are using an enterprise integration engine specialized in the healthcare space [2], with built-in single-branch version control and all actions going through the UI.

As I come from a background of several years with Ruby on Rails, I really hope to convince people to use this great library/framework your company created, since RoR is severely lacking when handling heavy concurrency like when gluing multiple APIs in complex workflows. Software engineers are going to love it, but integration analysts are used to IDEs with GUIs, so we'll need to create a pretty admin dashboard to convince them to switch.

[1] https://elixir-broadway.org/
[2] https://rhapsody.health/solutions/rhapsody/
Other have mentioned Rusty’s rules; in either case (Robert or Rusty’s version) the basic mechanics of parliamentary procedure are a useful framework. I don’t think I’ve ever been in a single organization where more than a few rules or basic principles are in active use in regular proceedings.
Not plenty and nowhere near as popular
Bolt: An Engine for efficiently eraining and deploying LLMs on commodity CPUs
All of the money? They've given it away for years, and they're just losing too much money.

Now one or two other companies can take all that, pay for one or two engineers and look like the good guys.
Thanks for the answer. Yeah, that's pretty much what I expected would be the case. Speaking as another dev in the AI space, it seems like reliability and consistency are the hardest issues when it comes to making AI genuinely useful in production vs. just a neat toy, and there's no stock solution.
Yeah that seems reasonable enough to me. I’ve seen parks and green spaces in Southern California that have warning signs about not drinking irrigation water.

My earlier comment was motivated by a concern that tapping a non-potable water source for one’s own family might bear health risks without more analysis of the state of that water. For all you know, even if you only use that water for plants, maybe you’re growing food with water high in arsenic and it’s accumulating in the food.
Do you have a preview?
Wouldn't that conflict with possible future optional static typing? It's only Stage 1. I'm hoping it doesn't make it in its current form. Some good discussion in the issues, though: https://github.com/tc39/proposal-type-annotations/issues
Can A.I. Detect Wildfires Faster Than Humans? California Is Trying to Find Out
I agree with the main points in the post and certainly understand how they could push one in the direction that htmx has taken, but for me (and I posted a long comment along these lines as a reply in this thread elsewhere) the benefit of TypeScript isn't just the type safety but also that it forces you to explicitly provide more strongly-structured, parseable context info (regarding your intent in the codebase) that can be used to further empower static analysis tools (whether it's the TypeScript compiler or various linters à la eslint and co) to pick up on discrepancies between what the code is supposed to do and what the code does.

I view JS as a particularly unreliable language to build solid (as in dependable, consistent, coherent, and sound) projects in, and the various build tools are just ways to at least partially overcome those inherent shortcomings of the language. Transpiling from ESNext to ES5, merging disparate source components, etc are all just icing on the cake and not the real reason to use TypeScript (though I am surprised that the article talked about its ECMAScript version restrictions caused by IE11 support but didn't talk about how w/ TypeScript you can use language-level (not library-level) features such as the spread operator, for ... of, async/await, etc. and have them automatically converted/transpiled to functional equivalents that work on ES5 browsers).

Just look at how the various @typescript-eslint/* packages can supplant basic eslint rules, replacing them with more precise variants¹ by using the extra information provided by the TypeScript AST instead of just the info surfaced by the JavaScript AST.

¹ Let alone the existence of the hundreds of additional lints that are only possible for TypeScript codebases.
This trend is indeed weird. It reminds me of my journey with Vim. In the beginning it was life changing. Like I felt like it really gave me an edge. I had all kinds of customizations on top of it. After a while I changed to Vim plugins inside full IDEs. No customization, just my plain comfortable text editor of choice. I feel nice while using it. Feels at home. I can't use mouse based text editors and feel happy anymore. Or at least I don't bother trying. Also I see no point in comparing this with anyone else using their tools. It's their tools and they could have more than a decade of experience in it.
I consider myself a pretty cynical person, but I tried it myself to prove someone else wrong and I couldn't help but feel like it actually worked.

We were looking for a water pipe, not just sitting groundwater. The only explanation I could come up with was that for some reason a magnetic field was being created by the pipe underground. I don't remember if the water was flowing or not when we did it.

I feel silly even commenting this, but we truly did find the pipe exactly where I was standing when the rods pointed together.

Of course it's very possible that I unconsciously tilted my hands in the spot where I suspected the pipe would be. Even though I did make a conscious effort to not do exactly that, I wonder if there is some psychological factor in the phenomenon.
Tesla Autopilot safety probe by federal vehicle regulators nears completion
You can also use a stainless steel infuser.
I think a key point is that (correct me if I'm wrong here) in predicate logic you can rewrite

∀x Fx

As

Not ∃x (not Fx)

Ie: "for all x, f(x)" implies the opposite of "there exists an x where not F(x)".

People seem to have less of a problem with

Not ∃x (not Fx)

when the universe is x is empty.

I usually explain it to junior developers by telling them to imagine it's a for loop over a list that returns true/false if it finds a value that doesn't match what's expected, and the opposite of it reaches the end of the list.
Is it?

If that case is so different, than the case with two marbles is also different - because removing the second-to-last marble will change will change the bag to be in that situation. But then, the case with three marbles is also different, and by induction you are left with only special cases.

On the other hand, see the related statement "If all marbles in a bag are black, adding a red marble will result in a mixed bag" clearly fails for the empty bag.

This isn't really a question of logic or mathematics. Mathematicians just use systems which are useful. And predicate logic, which has proven invaluable, would allow OP's claim.
> why can we just simply not do something new along the way

Marcin here, one of the member of the OpenTF.

99% of the value of Terraform is its ecosystem - providers, modules, tutorials, courses etc., and millions of lines of battle-tested production code already written in that language. 1% of the value is in the tool itself, with the tool serving as the gatekeeper to all these riches. One of the things that I personally want to see is opening up the codebase to allow building new things on top of it, which then don't need to reinvent the wheel.

You dislike HCL? Fine, have something else give the tool an AST and we'll take it from here. You don't need/want to go through the CLI? Not a problem, embed some of these libraries directly in your app.
I tried to come up with the most efficient implementation of this rather simple function that I could think of with pure Go without going down to SIMD Assembly: https://go.dev/play/p/zHFxwvWOoeT

-32.31% geomean across the different tests looks rather great.
Any ideas how to make it even faster?
Does http2 solve waterfall imports? Also wouldn't tree shaking still be unsolved? What about minification?

IMO build step woes are really overstated, my build step has linting, type checking, optimization, bundle analysis size diff checks, enables JSX, and is basically necessary for development anyway as you get hot reloading, compiler-added features for better debugging, etc.
> It is already in violation of the Acceptable Use ToS which implies they already have solutions in place to detect this behavior.

Putting it in the ToS is how they reserve the right to put in place solutions. But writing text in a ToS to ban some behavior does not magically create a working enforcement solution.

I'm quite certain they have spent the last few years: 1. Putting that in the ToS in order to give themselves permission to do the enforcement, 2. Working really hard fighting an enforcement arms race with people not complying with the ToS, 3. Losing the battle and painstakingly deciding to throw in the towel.

> It is easy to detect large amounts of disk usage with a high number of read/writes across wide swaths of the storage.

Again, these are active adversaries. Their first attempt probably fit that pattern in a way that was discernible to the dropbox client or server code, but it is unlikely that their current usage looks like that.

Again, false positives are extremely painful when doing account shutdowns for abuse. Other usage that is not crypto mining are free to exhibit "large amounts of disk usage with a high number of read/writes across wide swaths of the storage".

And again, I'm not saying this is impossible, just that it is actually a very difficult problem. And I am saying that I don't think it is at all worth the effort, and is much better to do what this announcement is doing, and not attempt to provide "unlimited storage" as a product at all.
I love this, particularly its clear-eyed summary of some of the tradeoffs. Gonna be honest: build systems have completely robbed the joy from writing simple frontend hacks for me. I no longer use them, which means I just can't use a whole lot of Javascript frameworks and libaries. Oh well.
It s surreal to read this comment in a SV VC supported forum

Like anti smoking posters in a phillip morris factory
Per client.
Compilers should be optional, in a two senses of the word:

1. Even if you use a language like TypeScript in your library, your users shouldn't have to. Provide types to them, even provide features like decorators, but have first-class and ergonomic ways for plain JS users to accomplish the same task.

2. Frameworks don't need compilers. All the reasons those that do claim to have them: especially performance, ergonomics, are disproven as requirement by libraries that meet or exceed them on those axes. You especially don't need to fork JS and HTML, and doing so fragments the web dev ecosystem, and causes tool friction, for very little gain. You can offer a compiler, but it should be an optional optimizer.

However, even as compilers should be optional, I also think they should be possible. If users want TypeScript to check their work, and especially if they're in large teams and organizations where extra checks help collaboration, your approach shouldn't prevent it.

And if you're doing things in a language without traditionally good static analysis tools, like HTML, you should try to provide them, otherwise your approach really doesn't scale due to ever-increasing fragility as your code base and team size grows.
If you WFH and your H is in a different state, for healthcare, are you subject to the laws of HQ's state, or the state you live in?

It's in interesting that for more personal decisions (i.e., child is transgender) WFH - or the lack there of - has sociopolitical impact, and is not simply work related.
Just checked online, he actually seems to be a russian citizen
In any discussion on languages like this, I feel the Wat discussion is always appropriate: https://www.destroyallsoftware.com/talks/wat
I love radio
> Its a phone for christ sake, they only last a few years

ah yes, "right to repair" was going so well, up until it led to a place you didn't like and then "it's a phone for chrissake, throw it away and buy another every 2 years".

what happened to e-waste concern, weren't you saving the planet?

like if your goals can only survive if you utterly steamroll everyone else's concerns and cross-purposes/goals that's probably not a goal that's accomplishable in a multilateral society, or at least your attitude towards those goals is unhealthy.

people want to know that a used phone isn't going to be full of shitty parts that diminish the experience, and we are trying to bias towards longer device lifecycles and more re-use. driving down cost to the absolute dropshipped-firehazard minimum isn't the only singular goal that people might have.

in fact sometimes these goals are inherently contradictory, like parts quality vs cost! cost encourages repair, but bad parts are also e-waste and every repair increases the likelihood of a total failure (damaged board, damaged back, etc). Shipping 27 batteries from amazon or china so you can replace them every 2 months is carbon-intensive and resource-intensive, on top of all the social issues it causes (like people who get upset and sue apple for "breaking their phone" when their knockoff part uses a legacy driver from an older phone that was removed from a certain iOS release).

in this situation, diminished trust in used products probably also has a negative effect on device lifespan and e-waste, and you've explicitly codified this with the "it's a phone, throw it away every 2 years" standard. That's not very eco-minded. You absolutely should care about parts, because parts keep those devices running and out of landfills.

If anything we should be pushing harder to force vendors to provide verifiable first-party supply chains with defined, long-duration lifecycles. Why can apple keep a battery or a display or a camera in stock for 10 years but google or samsung can't?
The people complaining about it are just biased. It's typical. Your outlook is atypical.

The reality is everyone is quirky and the only difference is most of this is hidden and covered up with lies and omissions.

Definitely this resume shows he's a bit less self aware and less aware about how other people think. But for a programming job, it's not a red flag.

People who call this stuff red flags don't realize the amount of shit people actually hide. The majority of people have 10x more shit worse than this completely hidden from the resume. This stuff is actually tame. People call it out because it's deviant.

The more serious shit like stole money from my employer or slacked off at work, all of that flies through the filters because nobody puts that shit on their resume and hiring managers are red flagging superficial shit like quirkiness and awkwardness. It shows how biased people actually are. They don't even know how to judge character themselves, they just rely on stereotypes of "professionalism" Just remember the truth about "professionalism"... it's just a way someone appears... It's not an intrinsic part of a human being.

In actuality the quirkiness of his resume shows he's a little bit more honest. He won't stab your ass in the back as he's open about other things people hide.

Actually... the other way to think about it is that hiring managers and coworkers only want to work with people who put up a façade. Nobody wants to deal with the true reality of how people actually are and if someone can't present a good facade he's not a good hire. But either way I would say the chances that this guy stabs you in the back in a really serious way are much lower than someone with a "professional" resume.

I'll be honest, I won't hire this guy based off of the same biases. But I admit my biases and I'm self aware. We don't actually have any real data on whether a person with this type of resume is more likely of ending up being a problem. Everyone just helplessly follows their gut and biases.