tauraamui

8 ms·

1.
by tauraamui 1y ago
They're not pivoting to go all in.
2.
by tauraamui 1y ago
I certainly did feel some of that in the past, but not anymore. I started using V for this project fully expecting it to go wrong, experience no end of issues, bugs, memory weirdness, edge cases etc., based on the many articles targeting V.
3.
by tauraamui 1y ago
I didn't mean to accuse you of being biased, I was just calling you not to be in case you were. I am sorry it came across otherwise. Your point of view is just as valid as anyone else. Also the editor project is completely separate to
4.
by tauraamui 1y ago
This AI answer is mostly referencing sources between 2020-2023. The only exception is an article written from last year, which itself admits "Anyone evaluating V for use today should obviously make judgement based on the language'
5.
by tauraamui 1y ago
It's in the docs but apparently doesn't work/isn't there any more. https://ziggit.dev/t/my-thoughts-about-async/4515
6.
by tauraamui 1y ago
I've not found any issues with using v for this project, please try and be unbiased and objective and I urge you to try and write a non trivial program and let the results speak for themselves. Up to you!
7.
by tauraamui 1y ago
They said years ago, when they last took a look. Just a thought, maybe just let all this go, people are complicated, you'll never please everyone. It's not worth the time trying. If anything you're giving them more ammo to pr
8.
by tauraamui 1y ago
Thanks.
9.
by tauraamui 1y ago
I'm happy for them :)
10.
by tauraamui 1y ago
So it begins...
11.
by tauraamui 1y ago
I've been finding it perfectly suitable for this and other projects. Have you updated your point of view after recently attempting to write and profile a non trivial program?
12.
by tauraamui 1y ago
Haven't heard of this, thanks! I'll definitely be taking a peak at their buffer implementation. Zig was a no go for this project for me due to the lack of concurrency.
13.
by tauraamui 1y ago
This is a good POV. For a while there they did think they had a chance at finally figuring out how to solve the halting problem. They of course haven't, and had no chance to do so, but they wanted to discover that for sure, for themsel
14.
by tauraamui 1y ago
Thank you everyone for commenting and sharing your thoughts regarding my project! I'm aware of the history of V and it's less than stellar reputation in the beginning. I really hope this comment section doesn't devolve into y
15.
by tauraamui 1y ago
Yes pretty much. Admittedly that's all the README needs to say. When I first wrote the project README LLMs were still relatively new for public use, it was much harder to detect back then. Thanks for the feedback.
16.
Lilly Devlog 1 – File picker ordering bug(tauraamui.website)
1 points by tauraamui 2y ago|0 comments
17.
A simple, efficient and lightweight double screen X window manager(github.com)
2 points by tauraamui 2y ago|1 comments
18.
by tauraamui 2y ago
The goal of this project is to show that it's easy to make your custom window manager, that we dont need to waste GBs of ram when showing windows and to provide a window manager that you can understand by looking at the code (so that y
19.
Lilly – A TUI Editor(github.com)
2 points by tauraamui 3y ago|0 comments
20.
Go code to concurrently recursively count file sizes in tree(gist.github.com)
1 points by tauraamui 6y ago|0 comments
21.
Dragon Daemon – IP Camera Streaming Server(github.com)
1 points by tauraamui 6y ago|0 comments