Feel like Mojo is worth a shoutout in this context https://www.modular.com/mojo Solves the issue of having a superset of Python in syntax where "fn" instead of "def" functions are assumed static typed and compilable with Numba style optimisations.
More of a question of /will/ Mojo eventually be entirely open source, chunks of it already are. The intent from Modular is eventually it will be, just not everything all at once and not whilst they're internally doing loads of dev for their own commercial entity. Which seems fair enough to me. Importantly they have open sourced lots of the stdlib which is probably what anyone external would contribute to or want to change anyway? https://www.modular.com/blog/the-next-big-step-in-mojo-open-...
Well the "expertise" is mostly just Python thats sort of the value prop. But yeah building an actual AI product ontop I'd be more worried about the early stage nature of Modular rather than the implementation is closed source.
Building on vapor carries a lot of risk. For all anyone knows they take a page from Mathworks and it winds up costing $20k+/year/license if you aren't an academic.
Genuinely curious; while I understand why we would want a language to be open-source (there's plenty of good reasons), do you have anecdotes where the open-sourceness helped you solve a problem?
Not the OP, but I have needed to patch Qt due to bugs that couldn't be easily worked around.
I have also been frustrated while trying to interoperate with expensive proprietary software because documentation was lacking, and the source code was unavailable.
In one instance, a proprietary software had the source code "exposed", which helped me work around its bugs and use it properly (also poorly documented).
There are of course other advantages of having that transparancy, like being able to independently audit the code for vulnerabilities or unacceptable "features", and fix those.
Open source is oftentimes a prerequisite for us to be able to control our software.
In the earlier days of rustc, it was handy to be able to look at the context for a specific compiler error (this is before the error reporting it is now known for). Using that, I was able to diagnose what was wrong with my code and adjust it accordingly.
Correct. If you run your own Postgres, you can install pg_search directly, otherwise we suggest our users integrate with their existing Postgres deployments (say AWS RDS) via logical replication: https://docs.paradedb.com/replication/pg_search
Came here to suggest this should be generic, but I'd also do something like pack in `man <command>` into the prompt if you are one shotting. Then it works for "all" commands that have a man page rather than just the commands GPT knows about before its cut off. Even just trying to scrape out `<command> --help` or something would be good too.
There area also a lot of people naive to how BS publishing has become. Plenty of PhD students get sucked in, a common one is being asked to publish your thesis as a book. Learning hubris comes before an embarrassment is a right of passage to the vast majority of people who think anyone really wants to read their thesis in a bound form from a third rate publisher created last year.
In some arts/humanities subjects publishing a book is equivalent to publishing papers. These publishers are filling the same gap as the lower quality pay to publish journals.
No you should strongly reason and believe in your own power of reasoning, but you should never dogmatically hold on to those beliefs in the light of new evidence that contravenes your previous ideas. Essentially all scientists that are even vaguely good follow this ideal. You have to know what is opinion from fact, facts dont change but your opinion about them does. Opinion guides generation of new facts. If you dont have strong opinions then you wont have the dedication to generate new fact. Look at the more zany side of religion, its strong opinion strongly held. They aren't capable of change and generation of new ideas. But if you were forever lacking in an opinion you also wouldn't action on anything and have some kind of existential nihilism all the time.
I think that says more about you than everyone else. I would walk halfway across town for slightly better bbq. Ultimately what is there to life than improving the quality of your experience. The issue is what consitutes better BBQ is completely subjective. So we might start from opposite sides of town and try and get to each others nearby BBQ ribs place. That's just human nature. With respect to "frameworks" some of this tends to be kind of centric to how you program. For the last decade most of my work isn't within any framework because its algorithmic with only a need for string IO and some parsers. Perl 6 for that is the framework.
If you come from only a Perl 5 background this is the issue. None of that is obvious. It is to someone who's seen OO languages that are a bit functional with good exception handling. In Perl 5 you would probably add to the top of the file:
use warnings;
use autodie;
To get similar functionality as the implicit Perl 6 IO error system.
Well if you are wandering that way again it's a bit faster a year later. About 10x across the board would be a good estimate. That's still super slow for some things.
