Communication in this sense is pretty common in Mathematics and Computer Science and it becomes apparent when its related to actors and their interactions.
A good example is game theory and game semantics. The term "actor" in this context are soo abstract that we can pretty much attempt to implement them anywhere we see fit and that I think is the beauty.
This is great but I feel like the potential is underused.
I know its a lot of work but I think we all could desperately use an interactive LaTeX notebook instead of limiting it to only the PDF backend and this work helps a lot with achieving that endeavour. Though it'll be limited to LuaTeX, it'll still be quite something.
It does not seem unreasonable to me as well and I do not recall stating that being the case.
I only mentioned the YouTube scenario, but that's pretty much the case for almost everything. I'll repeat it again: it all boils down to the personal bias of the admins, and you seem to agree with that as well.
To be clear, I was not talking about Odin specifically. This is about notability in general.
>where those third-party sources are themselves notable and reputable (in the subject area)
this is where the bias kicks in. It would be great if Wikipedia's notability goes "All youtube sources are not reliable" but instead its always phrased like "Some Youtube sources are not reliable" and what qualifies as this "some" is usually decided by the personal bias of the admins.
You make it sound like you're confusing popularity with notability.
Unlike Jai and V, Odin has been in commercial use(JangaFX) for years now with several high performance computing products written entirely in Odin and the customers of JangaFX includes several AAA video game and VFX corporations.
A lot of programmers not knowing or the language not being mainstream does not mean that its non-existent.
The Notability of Wikipedia is just the involved admin's opinionated bias. As simple as that. Its always been like that and it'll probably always be like that as Wikipedia seems like it isn't are capable of operating while changing that.
All the things you demanded require a significant amount of financial support to both create and maintain, and that is where Odin falls short. If you really do need all those libraries first thing in the morning, then forget about the language; it's out of your hands. You will always be at the mercy of the industry, and you will be forced to pick and use whatever language the majority of the industry is using while the industry keeps tailoring the majorly adapted languages to do things the languages weren't designed for in the first place.
Also, all the libraries you demanded have almost nothing to do with the language itself. Odin, as a solo project, lacks both the financial backing and the cult-like obsessive adoption within its community-both of which are essential for breaking into the industry and reaching the mainstream status. It's the industry's adaptability and the community's enthusiasm that determine how many new libraries will emerge for a programming language. Unlike modern languages like Rust and Zig, which have their respective foundation organizations that employ and pay several full-time developers, languages like Odin and C3 that stripped-down complexity and subjectively annoying features got no serious fancy features to market to the target consumers, making it hard for them to gain any exponential momentum. So, give the current state of things, we can certainly say that Odin will not provide any of those libraries any time soon.
Besides, the Odin developers are perfectly fine using libraries written in other languages, whether Rust, C, or anything else. If a library in another language works and will get the job done, re-writing it in Odin is logically pointless for getting the job done. The only people who seem to have an issue with Odin's ecosystem are backend developers. Low-level systems programmers and graphics developers have their needs well met(there are no built-in green threads or fibers but there is support for SIMD and all major graphics API bindings). Networking requires stable, secure maintenance, so unless someone from the community steps up to create and maintain an HTTP/3 or QUIC implementation, there will never be native HTTP/3 support in Odin. The same applies to Aerospike, YAML, JPEG XL, Slint, and everything else. Gotta see how things will turn out.
GingerBill and the Odin community put tremendous effort into making sure that the Odin compiler ships with "batteries included". You get base, core and vendor library collection that cover almost everything a developer would need to the point that you can argue that you don't need a package manager for Odin.
>He's quite insistent that Pakistan wasn't involved in the topical attacks.
Yes, just like how Pakistan was insistent about their involvement in sheltering Bin Laden. I don't understand why you expect any representative of a nation to confess explicitly to their crimes themselves but things like that just don't happen. Confession to their indirect involvement is the leading clue to majority of their actions and further investigation that will never be disclosed to public can only dig the truth.
>And indeed that the attacks may not have happened at all
that is very funny. That attack did happen and the attackers did send a message mentioning the name "Modi" to one of the survivors they spared. The tourists were stripped first to verify if they're circumcised and were shot immediately thereafter. I won't share further details but I ensure you, it really did happen and feel free to discard this as misinformation or dig further into it yourself.
I see.
If you are not satisfied with the shared source or think the video is edited to project a certain kind of perspective with ulterior motive, feel free to look further into it before completely discarding it was what I meant.
searching Yalda Hakim, Khawaja Asif full interview might point you in the right direction.
https://www.youtube.com/watch?v=ir8pJbKE37U
Why would they? Even the USA never admits their direct involvement straight away so its delusional of you to be expecting something like that.
If Pakistan is the kind of nation to confess, peace would have been established long back.
I would though. ELM has a very simple, straight forward syntax and everything revolves around the ELM architecture, which makes the whole thing very intuitive. I believe a statically typed and functional language will do just fine without any update for years as long as the initial implementation is done right. Unless there is a need to add some new feature, there is not point in updating the language if all the essentials were well implemented already. ELM compiles to JS and not to a native architecture. It'd be inappropriate to view ELM like one would view languages like C or any that uses LLVM as its backend.
No, its not. They are focused on introducing ELM on the backend as well. ELM isn't backed by big corpos like Rust and Go do so their way of operation will differ by a huge margin than those two langs, especially in terms of marketing so its inaccurate to judge that its dead just due to the inactivity.
oh no. At this point, we just need something that doesn't use the stupid combo of two languages(one markup and one style sheet) for UI and one(totally single threaded) for UX that allows people to share and view simple text and media to one another. Maybe then we can rid ourselves from constraints like having to stick to JS or a Virtual Machine like V8 while settling on poor implementations like WebGL and Canvas. WebGPU is still not a thing and it probably won't be anytime soon.
A new web browser or another JS runtime won't be the solution to the current mayhem. What could actually be helpful is an alternative to the "web browser" that operates on an entirely different stack than the currently JIT overdosed JS engines. But since everybody is well accustomed to and excited about improvements within the current madness(like this comment), adaptation of any alternative web browser like software will be highly unlikely even if it were several folds better at transferring media and rendering graphics with a much simpler approach and high performance. We are officially fo*ked.
its fine if you disagree and think that using "unsafe language" for low level hardware access is wrong but that doesn't change the fact that the more closer one operates to the hardware, the more bare-bone they need the tools to be or else they'll only get in the way of the job. Having to worry about something like a borrow checker or a reference counter just to manipulate a couple of bytes is not an efficient way to perform low level hardware programming.
Also, there is nothing wrong with any "unsafe language". Memory safety is a skill issue, not a language issue. All functional languages are safe and procedural languages are unsafe by nature. Its better to settle on a functional language and compromise on performance if memory safety is of utmost priority. The additional complexity and performance overhead of any supposedly safe procedural language is not worth it for doing low level stuff but it sure could be a fun choice when doing high level stuff.
This was never about the languages primarily though. The C programmers here would react the same way towards any other language, be it Zig or Swift, its not Rust specific. They just don't want to partake the additional headache they'll have to deal with to for making the Linux kernel more accessible to languages other than C.
Despite than, Rust devs kept on pushing it after all that was clearly stated, just to make things more and more annoying. Maintaining a software as huge and widely used as the Linux kernel is a huge responsibility that can't be relied on words like "leave it on our shoulders", especially when real time, immediate response is demanded. Development of something like the Linux kernel in Rust will be left unmaintained eventually, unless millions of dollahs are constantly invested into maintaining it because Rust is not as simple as C and the need to avoid accidental copying, memory leaks and almost all memory related issues will add more work because you can't escape "unsafe" when dealing with low level hadrware and C, making the usage of the Rust programming language for Linux kernel development utterly pointless.
I take potassium capsules frequently and magnesium capsules whenever I smoke, which is occasionally. Both of them were effective and help me with reducing anxiety and relieving stress.
A good example is game theory and game semantics. The term "actor" in this context are soo abstract that we can pretty much attempt to implement them anywhere we see fit and that I think is the beauty.