This just in from #cat-v on oftc.net:
| lot of fucking armchair systems engineers on 9fans these days
| the old dont get better, they just atrophy past their peaks
| it's definitely a lot of opinions. all of them don't matter
| I don't know why I posted politely instead of just saing "if any
I'm relieved this mailing list focuses on Plan 9, not 9front, since I don't use
9front. I submitted two patches today—no armchair engineers around here.
Besides ranting, move beyond it. Let it rest.
- Vic
On Fri, Oct 4, 2024, at 14:45, Willow Liquorice wrote:
> This just in from #cat-v on oftc
I agree with Willow. Zig would make an excellent addition to Plan 9. If it were
available, I'd certainly adopt it. I suspect it would also draw in a new crowd,
bringing fresh perspectives to the community.
- Vic
--
9fans: 9fans
Permalink:
https://9fans.t
Be confused no more: https://n-skvortsov-1997.github.io/reviews/
I found that link after a single search for 'v programming language
controversy' using duck duck go. It was linked from a hacker news post.
There are other resources. The controversy has made the rounds on numerous
tech news sites an
https://github.com/g-w1/plan9zig/
Quoth vester.thac...@fastmail.fm:
> I agree with Willow. Zig would make an excellent addition to Plan 9. If it
> were available, I'd certainly adopt it. I suspect it would also draw in a new
> crowd, bringing fresh perspectives to the community.
>
> - Vic
On Fri, Oct 4, 2024, at 11:25, o...@eigenstate.org wrote:
> https://github.com/g-w1/plan9zig/
Thank you. This looks promising, however two things have changed since the time
that was written.
1. std.Build has been renamed to std.build.Builder, which reflects Zig's
ongoing development and refac
I believe you're misinformed about bootstrapping Zig. The link to the
Zig README in my previous email is to the section that describes how to
bootstrap Zig *using only a C compiler*. For more details, refer to my
previous email.
The most annoying thing about Zig, potentially, is the "package m
I must admit that my rather non-committal email on V is largely down to
my low appetite for years-old programming language drama. Wikipedia is
also far from comprehensive.
Nothing is quite there yet as a "new language" for Plan 9. Rust is *too*
abstract and is quite baroque (see: custom alloca
try this and it should make sense:
x/.+\n.*/ x/\n/ d
with .* to the left of the \n you get the following:
match foo\nbar and delete the \n
match \nbaz and delete the \n
match \nqux and delete the \n
match \nquux and delete the \n
match \n and delete it
umbraticus
--
Now I see. Thank you.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tabb641f45805a1fc-M5d177572b05eceebe0335e0a
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
I am confused by the divisive views on V. On one hand people who seem to know
their onions speak well of it. @Willow provides helpful reasons why the project
might have started inauspiciously, whereas by contrast @Noam I feel you cast
vague aspersions without evidence. Perhaps for a fledgeling l
Consider the following sample text:
foo
bar
baz
qux
quux
The purpose is to merge each pair of words, so that the text becomes:
foobar
bazqux
quux
The following command works fine:
x/.+\n.+/ x/\n/ d
But the following one does not:
x/.*\n.*/ x/\n/ d
It results in all \n being deleted.
I supp
They've made ridiculous, obviously-false claims. You can look it up
fairly easily if you want, I recall articles titled "V is for Vaporware"
and the like from a few years back.
the very short explanation: they have had outright lies on their website
since, IIRC, 2018.
They have still not fixed th
ThePrimeagen has put together a couple of solid videos on Vlang, blending
entertainment with valuable insights.
1. In this reaction video, he dives into Vlang with his signature mix of humor
and curiosity.
https://www.youtube.com/watch?v=j47Hk5qE9As&list=PL6Vr-1-zVu5CUQOoZa-3BYYbYJ1CGlpRH
For a
14 matches
Mail list logo
