Hacker Newsnew | past | comments | ask | show | jobs | submit | systems's commentslogin

its open source, we can fork .. (i know for such a project it will require a very special group of "we", but in theory .. it can happen)


If you need a fork, I've already done most of the hard work for all of you.

https://query.farm/haybarn/

Or

https://github.com/Query-farm-haybarn

I've been releasing the versions all the way since 1.5.3 and all community extensions.


> a self-contained, signed extension ecosystem

What does this mean? Can I easily sign my own private extensions with my own key?

We are currently allowing unsigned extensions, loading them, then locking the duckdb config to prevent loading unsigned/untrusted extensions


In 2.0 you can sign extensions with your own key and have your own extension repo. Thats the plan at least.

In 1.5 - Haybarn has its own signing key, but its much faster to get extensions released and deployed.


for me the highlight of this release is the docked speedbar, it took them too long, but its finally here

dired mode is fine, and i appreciate it, but having the folder view docked on the left, was something i missed in emacs, happy its finally here


C++ succeeded because it was Object Oriented, people didn't start talking about RAII as C++ killer feature until years later

python succeeded because it wasn't Perl's TMTOWTDI, everyone expected ruby to overtake python, but .. for some reason that never happened

swift succeeded because apple pushed it to replace objective c, that if you consider swift succeeded

anyway, i agree with your premise, languages need one key strategic advantage feature to succeed, but you just got it wrong on few of them .. and if i am wrong too, then the premise is weak, if we are not sure what the killer feature is, we then have no idea why the language succeeded


I don't think C++ succeeded because it was object-oriented. I think C++ was object-oriented because classes were an abstraction that could layer on top of C with fairly low overhead, giving it more expressive power without much mandatory cost to size or speed.

In other words, object-orientation was the means, not the end.


Back then OOP was all the hype and inheritance was cool.


C++ predated the OOP hype cycle and triggered, or at least accelerated it.


Agreed and that's probably the second major killer feature of C++.


> python succeeded because it wasn't Perl's TMTOWTDI, everyone expected ruby to overtake python, but .. for some reason that never happened

Ruby allows (and to some extent encourages) unreasonable code.

It's not bad code (and in some cases extremely elegant), but it's code you can't reason about.

Being able to open any class (or object) and add new methods to it makes tracking how execution works extremely difficult.

The language allows for very undisciplined things to work - its great for the "scripting" and rapid prototyping - but unless you're going to throw it away the next day of having to maintain that code it starts weighing on the future speed of working.

Undisciplined code can be handled by making sure everyone on the team is disciplined in its use and documenting how things work... but that rarely reflects reality.

And so, you move to a language that enforces more discipline in how one uses it and is more reasonable in its execution.


Ruby felt like a better Javascript, but JS ran in the browser, and so had the constraint of the DOM...

Aka you have to be (more) disciplined within the constraints of the browser.

I'm not saying JS was good...

The lesson here being, complete freedom is fine, as long as you are also able and willing to implement a strategy to verify your operation, ruby on rails, js in the browser, python PEP or pythonic ways...


I came to ruby from the perl side. It was "here's a Redmine server, here's a feature request for one of the in house built plugins." I forget the specifics (it was 2011) ... but trick of the feature was to add a function to the object being created so that it would have the function some other module was expecting. And it worked...

Things like that made me give it the sideye for anything more than I could keep in my head at once... if I started needing to look at other files to determine if there was anything odd there... "can I create a function here in this parameter passed to me? What if someone else created a function of the same name before they passed it to me and expected it to remain?"

It can work... but it requires a bit more discipline than the developers I was working with had as a baseline (for that matter, a decade and a half later at a different job with a lower baseline and AI code - the idea of that terrifies me).

It's a "powerful" language, but I think it has too much power.

I like groovy for much the same reason that I liked perl and ruby (to an extent) - but it too is too powerful. It's great for writing scripts where it's a file or two or three... but if the "what does it do" gets too large to keep in my mind at once then it requires more discipline. I like to think that I have that discipline when working solo in groovy (and people will tell me I don't need to be that explicit in the objects... creating a class file rather than just shoving anonymously built objects into a hashmap), but that's how I can come back to old code more easily.

Ruby Conf 2011 Keeping Ruby Reasonable by Joshua Ballanco https://youtu.be/vbX5BVCKiNs

Abstract Heresies : First-class environments https://funcall.blogspot.com/2009/09/first-class-environment...


C++ succeeded twice.

Initially, it provided a thin object-oriented abstraction over C. This solved many problems scaling large C projects. It set baseline expectations for languages that came later. Being a "thin object-oriented abstraction over C" has significant limits. By the 2000s, it was clear that C++ couldn't scale complexity in the way we needed it to. It was slowly dying.

C++ reinvented itself as a functional metaprogramming language starting with C++11, providing an even higher level of abstraction. Many deficiencies in the older language and systems languages generally were addressed. This was a huge success, creating a large resurgence in adoption and setting new expectations for what a systems language should be capable of. C++20 looks like a completely different (and much better) language than C++98.

I view C -> legacy C++ -> modern C++ as the evolution of a single language. Each was wildly successful on its own up to some level of complexity. Every time it runs into a practical limitations on scaling complexity, it adds a new layer of abstraction. As much as people complain about it, this strategy has clearly been successful.


This is an interesting take, although I'm not sure the legacy -> modern evolution is perhaps quite as significant as you make it out to be. Smart pointers and better std library constructs are absolutely welcome, metaprogramming is nice, but perhaps out of reach for many programmers (so not the "fun" or "successful" part of the language)...

If you were to compare the transformation with another major systems language, or a popular dynamic language, it doesn't feel like the evolution is quite as dramatic as is made out to be?

Rather, the staying power comes from elsewhere, and the language continues to modernize, perhaps at a slower pace than other contemporary languages experiencing similar staying power(s)...


its a specific type of language, not all language are the same , the nature of that specificity is the main point of the the claim made in this article


all languages are embedded in some domain, therefore having a domain does not make a language "a specific type of language"


People have settled on the term DSL to identify those languages whose domains are highly constrained as compared to more general purpose or broad domain languages. This usage exists whether or not you think the term itself is stupid.


I know what they meant to do, but they've drawn a line where no line exists and the result is confusion.


I don't see much confusion


Many languages are in fact designed and publicized as general-purpose programming languages.


how are they obviously semi shady? whats shady about brave?




yea this is bad, i had kinda forgotten about this https://github.com/lobsters/lobsters-ansible/issues/45#issue...

i dont know, firefox is very buggy and unstable, crashes or just log me out of everything every few weeks, we dont really have great choices, wishful thinking, but i hope brave straightened up


Yuck! I'd heard of these but I am always like "it IS open source". But so is Mozilla. I actually did test a build of Ladybird. The sites I looked at (without login or anything) basically all work fine but they are VERY slow. This is understandable. Performance is not their priority right now. It is coming along fine though.


the use case for sql to er, is to study a database new to you

so the db already exist, but they have no er, and maybe even little docs

so it act more like an exploratory tool, ideally, it should allow you to create views and add notes, so you dont have to look at the full er at once, especially if the number of table is huge, and if many of those tables are missing foreign keys


its 43 CAD at amazon so no

a book like this should be 20-25 CAD max specially since its clearly a pop corn read .. "I won't pretend I have this all figured out" .. I don't think anyone should pay 43 CAD to read you thinking out loud (the lean startup is 25 CAD by the way, with a 10% discount)

if ever it goes on discount on amazon, maybe


You can always use the library


Strongly endorse this way of thinking. If your local library doesn't have enough copies, I'd be glad to donate one.


well, it also made by the same guy behind the boring go book which probably means that boring go is also most likely AI generated

nowadays before reading or buying any book, we need to extensively investigate the author, the author name is now more important than ever, i think whenever a book is shared, the author need to me highlighted


That guy’s entire post and submission history appears to be listicles and slop.


> nowadays before reading or buying any book, we need to extensively investigate the author

I mean not really. You read a paragraph or two and notice the quality of the text, start getting suspicious and continue two or three paragraphs more, notice some very basic inconsistencies/incoherence, realize it's AI-written and ctrl+w the tab (or put back the book in the shelf) and move on with your life.

If there is no samples of the book, I'd hesitate to even consider buying it, just so you can actually sample the text. Very easy in bookstores luckily, so not a huge problem in the end.


You can just read a paragraph or two of each email, and then decide whether or not to delete them. We don't additional tools to combat spam.


Kind of feels like a slightly different thing, I don't spend days/weeks reading through one email.


If someone wanted an AI generated Zig tutorial, why wouldn't they go to their favorite LLM supplier and simply prompt the AI for one? Why do we need someone to create this spam ahead of time? LLMs are improving all the time and Zig is a moving target. Seems like a win-win-win. The end-user gets a better (and potentially customized) tutorial for the latest Zig, and there is less overall spam pollution.


I don't have the answers to those questions, and I don't know why I'm being asked those either. I don't like AI-slop either, I don't think anyone except the ones who produce it themselves like it.

But ultimately it's a fools errand trying to stop/get people to do something, best you can do is adjust your own approach.


we don't pay for emails either

i think for consumer protection, AI products need to be flagged as AI products, clearly labelled as AI produced or assisted , of course for free goods the burden is on us, but for anything we pay for, I hope we get this protection


do you mean use none core libraries / 3rd party libs or using libraries from different languages like how some libs or frameworks from different languages create bindings to python libs

many C# libs are available via Nugets, which are not more or less complicated than other languages package managers

i personally think C# package management is more obscure, compared to other languages


I mean that in both cases, the core language platform provides the tools and libraries you need to develop complete applications; you don't have to introduce external dependencies or resort to writing low-level data structures and data types.


this is a who comes first, chicken or egg

Nim is one of those languages that tries to be everything for everyone, trying to fill the range from python to C++

If Nim had any strategic edge anywhere, someone smart would have picked it up to build something very successful and it would have had more sponsors


It sits in the sweet spot for projects like nitter--which is not the kind of work that's attracting investment right now, but that's due to markets being a clumsy tool for deciding what should be done and nothing to do with Nim's merits.


Being a generalist isn't easy.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: