swasheck

windmills cause cancer and kill bald eagles so we can’t do wind. /s

IP theft may only be part of the story though. it’s a question of priorities. US optimizes for profit which can place limits reinvestment. China seems to optimize for ubiquity and dominance, and has the capital to throw at those goals. when you’re beholden to the shareholder/ceo/investor, you make concessions to stay within their will. when you’re beholden to the state, you do the same.

the next season of natural selection just dropped. pop the corn (in olive oil, natch).

there is no logic - just fallacy. it is a red herring, wrapped up in equivocation. he commits appeal to emotion, non sequitur, false equivalence along the way.

this is how i took it as well. he’s creating a false equivalency between AI and immigrants, and attempting to justify it with “diversity of perspectives” and trying to tell you that to remain intellectually consistent you must embrace or reject both.

clicking a link to in the Contents section opens a new page instead of jumping to an anchor. wonder if he's getting paid by the click.

thank you. really appreciate that insight.

please educate instead of insult. happy to hear your response. that is why we’re here, after all.

agreed. i’m no aws apologist but if you’re going to try to monetize open source and then complain when someone else does it more efficiently/effectively, it really feels disingenuous. “we were going to do that, but they got there first. it’s not fair.”

i’m only familiar with the postgres side, but it seems like a more nuanced view of this debate would be to discuss aws monetizing open source relative to their upstream, community-beneficial contributions.

the pricing “API” is also a joke so it’s not like they have tried pushing people to apis and away from the console.

i just use vantage (https://instances.vantage.sh/) now. their api is functional and reasonable.

it was patently obvious. people were just blinded by xenophobia as the primary issue facing the nation and they bought it, peripheral consequences be damned

i created a program to make it appear like i wiped my formulas before before a calc 2 final in high school so that when the teacher witnessed us wipe the phones it seemed legit.

zero _immediate_ results. hate is a powerful motivator and hard to overcome, and the political machinations also don’t really allow for immediate feedback. we will see what happens this midterm cycle. polls show repudiation of the current administration across all dimensions.

as were the protests in the 60s. violent uprisings give greater permission for violent suppression. nonviolent protests that are met with violence draw greater scrutiny. the american behemoth rarely turns quickly.

along those lines, this is a “fun” (albeit tangential) read https://x.com/PalantirTech/status/2045574398573453312?s=20

people really do struggle to differentiate between correlation and causation. we humans love our patterns so that we can make sense of existence.

i think "SELECT * FROM my_df" is a convenience from the python module and how tightly integrated it is, but i can’t get this to replicate using the cli or dbeaver or datagrip.

and yes, being able to layer analytical sql on top of your csv/json/parquet/gpx/arrow (but not xml?) is the massive appeal of duckdb for a variety of reasons. it’s a paradigm shift for me as an old timer but it’s also suited my needs quite well over the past few years

must be a seasonal thing. i’ve never seen nobody but have also never seen disney.

whether or not you agree with the author's conclusions, most of his rationale behind them is spot on. yeah GC is majestic and amazing from the bottom up, and if you find the hidden gems within the park then you are golden. but the average experience is a solid “meh.”

was disappointed to see the great sand dunes omitted from the list of the worst. people obsess over those and every time i’ve gone it’s been a unquestionably miserable experience, not to mention a general letdown

i think we need to encode (or refine) what we mean by “vibe code.” my original impression was that it was used to describe the process whereby someone with an idea but lacking development/engineering skills leveraged llm via an agent to create the mechanics to bring their idea to fruition. anymore it seems like if it has the hint of AI then it’s “vibe coded.”

ironically, i didn’t read the article because i come to comments now to see if its been identified as AI slop, so i don’t know which area this falls into

ok. thanks for the correction. that’s good information that helps me overcome some of the FUD i’ve received

negligence (especially via ignorance) is a thing. a hobbyist wanting to celebrate their first batch with their buddies can poison them with some smeared hearts. but i get what you’re saying.

it has been my go-to provider for things but i noticed extraordinarily high usage rate last month on a little side project i started so that i could learn about things that are interesting to me while helping my day to day responsibilities (creating an iceberg data lake from my existing parquet files). i used my month’s worth of corporate subscription allocated tokens in 3 days. never seen that before so now i’m a lot more apprehensive about getting into the weeds with claude but i’m also so much less impressed with the other available models for work in this domain.

i appreciate the way you took the feedback. i saw the domain name and immediately knew the content and context. the article did not disappoint. i come from a heavy mssql background with some postgres sprinkled in, but my current company is migrating our mssql fleet to pg and it’s nice to have a technical foundation and article to be able to truly understand and pass the differences and similarities then how the two platforms handle workload. Traditionally it’s just been multiple sides, mercilessly criticizing each other for their deficiencies, but each platform has its own strengths and its own gaps. I’m excited to be a part of this migration, and I appreciate technical articles such as this that help me articulate the broader challenges to both our executive level levels, and our developers.

edit: syntax. voice to text was liberal with the comma abuse

HyperCard was a revelation to me in high school. it piqued such an interest in technology for me that i fully pivoted from exploring civil engineering to computer sciences.

> happy to stop the freebies we give other nations.

but indignant when other nations return in kind.

one of the things that i noticed in a recent trip to austin is that the waymo vehicles were far more assertive and quick than the human drivers so maybe that has been addressed.

so happy to see Sapiens in there. what an obtuse read. here's a fun "if books could kill" episode on this work of pseudoscience https://podbay.fm/p/if-books-could-kill/e/1763632800

this isn't purely laundering blame. it is frustrating for the infrastructure/operations side is that the dev teams routinely kick the can down to them instead of documenting the performance/reliability weak points. in this case, when someone complains about the performance of the site, both dev and qa should have documented artifacts that explain this potential. as an infrastructure and reliability person, i am happy to support this effort with my own analysis. i am less inclined to support the dev team that just says, "hey, i delivered what they asked for, it's up to you to make it functional."

> From the perspective of the devs, they expect that the infrastructure can handle what the business wanted. If you have a problem you really should punch up, not down.

this belittles the intelligence of the dev team. they should know better. it's like validating saying "i really thought i could pour vodka in the fuel tank of this porsche and everything would function correctly. must be porsche's fault."

thanks. now i see the point that the poster was making.