There are Python interpreters written in other languages: there is one in Rust, and there is Jython and IronPython.
592 karma · joined January 21, 2013
There are Python interpreters written in other languages: there is one in Rust, and there is Jython and IronPython.
Whatever can be compiled to BPF meets this requirement. The price though is that it wouldn't be very useful.
There many initiative around wasm, one of them being WebAssembly interface types, aimed at that problem. This makes using wasm simple.
This may work for most people, but not all. It's easier to get things fixed while developers still work on something, than weeks/months later. Also if you have not most-popular hardware/software configuration, testing done by others isn't necessarily sufficient for you.
And it sometimes is.
> If a change breaks it, some one will probably have called read(2) a few times before that kernel is shipped to you.
I've seen to many kernel bugs on new hardware to believe this is enough. Maybe not in read(), but still in something that should work. Throwing testing on users may have been acceptable in the past, but not anymore.
Yes, you do, because otherwise you will find that some change or new hardware will break it.
Also "taming text"
sort-of possible now (frozen*)
> pattern matching
That has been added recently
What academics produce is most likely proof of concept or a prototype, not something you can "refactor" and ship. It's not a matter of tooling and programming languages, but of what is actually produced. Software engineers produce software that meets all sorts of non-functional requirements, experts care about functional side only. So get all sides to agree on what will be produced and then ask developers about how they will proceed with putting that in production. It may require redoing most or even everything.
> They also don't seem to have a big sense of the urgency needed at my small company.
You don't do creative work to a schedule, especially urgent one. The only thing you can predict reliably are the ones you have already did (and only if the circumstances don't change). People promised self-driving cars long time ago, and we still don't have them, regardless of any company sense of urgency. You deal with that issue by discussing stages and scope of delivery with all sides, not by expecting their understanding of urgency.
> It doesn't seem like they should be treated as a separate team because too much will get lost in translation
That's true, getting managers to act as translators between experts and technicians is a really bad idea.
> How do I set timelines when it's hard to understand the work?
You ask them to set them for themselves. You don't need to understand the details, you need to understand what will be produced and how all involved sides will use it and that they all agree here.
> Should they integrate with software best practices or just be their own thing throwing successful R&D over the wall?
That depends, but most likely you will have more success passing what they do to your developers (who are great at being software developers) than by teaching software development to someone who doesn't understand it. Some training may be beneficial though (so that their work can be used by developers).
No. People do not perform system updates because a) it's a chore and b) it get's in the way or even breaks things. To do an update I need to agree to give up control over my device for some time (often undetermined) and then risk that updated code causes issues (it's not uncommon). We need to design apps and operating systems with seamless and reliable updates in mind, not force people to suffer.
Perhaps, but not directly. It will depend on some libssl-rs which depend on libssl-sys which handles C bindings, so that application authors don't think about it.
Dozens of other languages that are tiny and new do not have good packaging story. Rust does, because it cares about developer experience.
> Wait until you have Rust packages which include and wrap hundred of thousands of lines of very old C and Fortran code like numpy has.
I don't know about Fortran, but C is basically legacy at this point, it doesn't change much and even if it does, there is one some-c-lib wrapper package that takes care of all those issues, Rust apps rarely depend on some C dependency directly.
Is it a licence (in practice) for a right to brand name or really the look? Could Forza make a model that looks almost exactly like a Ferrari but name it Furrari?
What your company poor time organisation has anything to do with development methodology?
but...
we have clouds now, so even if you find something, development will require CD/CI pipeline, github actions and so on.
There was a language like that once, it was called HTML. It had very basic set of features initially, but then someone needed text to blink, someone needed to display videos, someone needed to send forms, someone needed to use it to play games and here we are today, and it's not done yet. If it was implemented today, you will get exactly same result in near future, because everyone's "small set of features" together adds to infinity.
To catch a chicken you need to be slight faster some of the times, not much of intelligence necessary. (You will need a lot of development of internal organs to be slightly faster though).
You can mandate them to be if you are building something that uses them. If you don't have control, than its up to someone else to decide, and people wanted to be able to link remote resources.