I for one appreciate a public figure with a wildly opposed mindset to the Silicon Valley/VC-Funded/Ultrascaling/whatever crowd.
The pushback is warranted and on point, especially the technical points. It has taken a suspicious amount of time to produce the fabled blog post which I don't think states almost any new information beyond what Jarred has already shared on twitter. The one (and very interesting) exception is the theoretical price of the rewrite via the API pricing.
Miro is a native pdf viewer for Windows and Linux (and macOS) built with iced and mupdf-rs.
Following some momentum from the last update we've managed to push out another release! This one contains two long await features; searching through documents and reading annotations (or comments).
As with most PDF readers, searching through the document is done via plain text but in this case can also use regular expressions! I wanted to try fuzzy finding as well but found no good way of chunking the pdf into a list of strings to search through. Do hit me up if you have any good ideas in regards to this, fuzzy finding is the best search method in my opinion and I would love to support it.
Annotations, or comments as they're sometimes called come in many different forms. Mupdf could already render the in-page annotations just fine which left me with the task of showing something for the sticky note annotations that pop up outside of the page. With some small upstream contributions to mupdf we could extract the contents and bounds of these sticky notes and show them in a simple popup which moves relative to the page.
Whenever I get around to it, I think the next release will introduce some editing functionality to annotations. That is however a big step for a program that has only been reading PDFs thus far.
Seeing as I'm attempting to build my own CAD program in Rust I checked out the hosted website. I'm not really sure what is supposed to be working and what isn't.
I can't help but to be skeptical of one person writing ~115k LOC in 4 months which is just the Rust crates, nevermind the frontend (which is another 100k LOC!!!).
I'm curious why you decided to go with "eager" tessellation. Creating a circle immediately results in a bunch of lines which resemble a circle but would fail under tangency constraints quickly. Is this a current limitation or part of the strategy for the kernel?
I've been trying out Zed for a while now and it's been a nice experience for 90% of the time. What bothers me the most is the half-baked Vim mode. Granted it is better than almost all other Vim modes in other editors, but it is still not incorporated everywhere.
Switching to non text panels like the git sidebar is something I've just not figured out well. I can get there with a keybind, but focus is never in the right place to allow me to navigate the git sidebar with the Vim controls it already supports.
If this could be solved I think I would make the permanent switch.
Include a screenshot in the readme before sharing your projects. I am not going to install your neovim distro just for a chance of seeing what it looks like
> Writing design documents, properly tracking decisions, careful planning, building infrastructure and deciding on expensive infrastructure projects, all sorts of compliance stuff.
These are important skills as a data scientist as well and as such shouldn't be new for you. I'm not sure what sort of strategy you've been employing to get any serious data science work done.
> how do I get better and find joy in the more managerial tasks of software engineering?
Maybe you don't and that is okay. You don't have to find every single part of software engineering joyous. This goes for non-managerial work as well. Not all problems are blessed with being fun. Just do it regardless.
> Does confidence just come with experience?
Yes.
> Can I get better faster?
Yes. You get faster at any task you repeat often enough.
> Or is it all worthless anyways and I should focus on the code?
Some of it, maybe, maybe not. You'll know what kinds of non-programming activities help your programming after trying them out for a while. I for example don't love design documents for every little mundane feature. However, for larger, complex tasks the act of writing something, anything at all helps me bring clarity to my thoughts. I've also found development diaries extremely useful for any project where I go more than a week between development sessions. The important point is that I found this out by testing it out and reflecting on my experience and/or results.
This can be asked for basically any non-trivial GUI application. Why doesn't linux have:
- Photoshop
- Premiere
- CAD software
- Lightroom
IMO the answer is the lack of good UI toolkits for linux, with any sufficient definition of "good". GTK or Qt are probably the closest solutions to Win32 or WPF, but I think we can empirically just say that they are not "good" enough. If they were, more complex GUIs would exist.
Of course Zathura + any backend works through XWayland. But as mentioned I also use Windows and want to use the same program (or something with the same key bindings) on both operating systems
Of course Zathura + any backend works through XWayland. But as mentioned I also use Windows and want to use the same program (or something with the same key bindings) on both operating systems
Of course Zathura + any backend works through XWayland. But as mentioned I also use Windows and want to use the same program (or something with the same key bindings) on both operating systems
MuPDF for sure has most of the capabilities of interacting with forms. But for my workflow I mostly create and read pdfs, I don't fill out much information in partially complete PDFs.
Comments or annotations are in the planning stage though