はてなブックマーク

The habit is in the 7th paragraph, after 2 images:> Rather than trying to complete your task in 20 minutes, take this time to write down your thoughts, and a step-by-step action plan of what you think you need to do to finish your task. Then go home. Rest. A feeling of incompleteness will motivate you to come back and finalize your work the next day. Only you will be full of energy, together with

I actually don’t like python type hints!At my work we have a jit compiler that requires type hints under some conditions. Aside from that, I avoid them as much as possible. The reason is that they are not really a part of the language, they violate the spirit of the language, and in high-usage parts of code they quickly become a complete mess. For example a common failure mode in my work’s codebas

We now live in a world where KDE looks nicer, more professional, and more consistent than the latest macOS. I don't know how that happened, and KDE isn't even particularly nice looking, but here we are.For many years now KDE has focused on polish, bug fixing and "nice-to-have" improvements rather than major redesigns, and it paid off. KDE is, as its name implies, a desktop environment. And it hasn

For AI you definitely need to clean up and I think even targeted learning on some practices would be beneficiary ; for users ; it depends on the people, and I'd argue that vibe-coded rust can be better than just "written-rust" IF the important details and mind of the user are actually focused on what is important ; Eg ; I could vibe-code a lock-free well architect-ed s3 - focus on all the importan

The author gets close to what I think the root problem is, but doesn't call it out.The truth is that in python, async was too little, too late. By the time it was introduced, most people who actually needed to do lots of io concurrently had their own workarounds (forking, etc) and people who didn't actually need it had found out how to get by without it (multiprocessing etc). Meanwhile, go showed

What bothered me for a long time with code reviews is that almost all useful things they catch (i.e. not nit-picking about subjective minor things that doesn't really matter) are much too late in the process. Not rarely the only (if any) useful outcome of a review is that everything has to be done from scratch in a different ways (completely new design) or that it is abandoned since it turns out i

I've been burned too many times by embracing open source products like this.We've been fed promises like these before. They will inevitably get acquired. Years of documentation, issues, and pull requests will be deleted with little-to-no notice. An exclusively commercial replacement will materialize from the new company that is inexplicably missing the features you relied on in the first place. Fo

I'm involved with this project and wanted to provide some context. This is an extraction for a much larger effort where we're building a web browser that can render native UI. Think instead of:`<div>Hello, world!!</div>` we can do: `<Text>Hello, world!</Text>` I want to be clear: this is not a web renderer. We are not rendering HTML. We're rendering actual native UI. So the above in SwiftUI become

We've tested almost every visualization library under the sun when building Briefer (https://briefer.cloud) and I can confidently say that Apache ECharts is the best.The main issues with other libraries is that they're either: (a) ugly (b) difficult to use (i.e. having to do things imperatively) (c) not flexible enough Apache ECharts solve these 3 problems. It's pretty by default, it allows us to

Looking at the sparse documentation of openrsync does not create any confidence for me that it can be an acceptable substitute for rsync.In my opinion, any program that is supposed to copy files, but which is not able to make perfect copies, i.e. copies that do not lose any bit of data or metadata that was present in the original file, is just unusable garbage. Unfortunately, most copying programs

Already see people saying GitLab is better: yes it is, but it also sucks in different ways.After years of dealing with this (first Jenkins, then GitLab, then GitHub), my takeaway is: * Write as much CI logic as possible in your own code. Does not really matter what you use (shell scripts, make, just, doit, mage, whatever) as long as it is proper, maintainable code. * Invest time that your pipeline

512GB of unified memory is truly breaking new ground. I was wondering when Apple would overcome memory constraints, and now we're seeing a half-terabyte level of unified memory. This is incredibly practical for running large AI models locally ("600 billion parameters"), and Apple's approach of integrating this much efficient memory on a single chip is fascinating compared to NVIDIA's solutions. I'

Curious if anybody out there is trying to build a new model/architecture that would succeed the transformer?I geek out on this subject in my spare time. Curious if anybody else is doing so and if you're willing to share ideas? The MAMBA [1] model gained some traction as a potential successor. It's basically an RNN without the non linearity applied across hidden states, which makes it logarithmic t

> The cost to use a given level of AI falls about 10x every 12 months, and lower prices lead to much more use. ... Moore’s law changed the world at 2x every 18 months; this is unbelievably stronger.Moore waited at least five years [1] before deriving his law. On top of that, I don't think that it makes much sense to compare commercial pricing schemes to technical advancements. [1] http://cva.stanf

Counterexample: Ive been able to complete more side projects in the last month leveraging llms than i have ever in my life. One of which I believe to have potential as a viable product, and another which involved complicated rust `no_std` and linker setup for compiling rust code onto bare metal RISCV from scratch.I think the key to being successful here is to realize that you're still at the wheel

OpenAI has a very healthy revenue stream in the form of other companies throwing money at them.But to answer your question, no they aren’t even profitable by themselves. > they aren’t even profitable Depends on your definition of profitability, They are not recovering R&D and training costs, but they (and MS) are recouping inference costs from user subscription and API revenue with a healthy opera

I am most excited about the parser change, previously discussed here:https://news.ycombinator.com/item?id=36310130 - Rewriting the Ruby parser (2023年06月13日, 176 comments) I remember being taught to use yacc in our compiler course because "writing it by hand is too hard". But looks like Ruby joins the growing list of languages that have hand-written parsers, apparently working with generated parsers

I am totally fascinated by programmers who don't use many of the IDE features I take for granted today: autocomplete, language servers, and recently copilotSo to the devs who don't use these tools, how do you do it? Do you just remember every type and field in a codebase? What does your flow look like? One example is that I cannot live without the language server go-to-definition feature. What do

The thing that the author says they would prefer is already in Python, it's called NewType (https://docs.python.org/3/library/typing.html#typing.NewType)They say "...so I can't create a bunch of different names for eg typing.Any and then expect type checkers to complain if I mix them." `MyType = NewType('MyType', Any)` is how you do this. At the end, they suggest a workflow: "I think my ideal type

Question for the group here: do we honestly feel like we've exhausted the options for delivering value on top of the current generation of LLMs?I lead a team exploring cutting edge LLM applications and end-user features. It's my intuition from experience that we have a LONG way to go. GPT-4o / Claude 3.5 are the go-to models for my team. Every combination of technical investment + LLMs yields a ne

F# has been my favorite language since I first encountered it in uni. F# was/is waaaay out ahead of C# with features like unions, null safety, pattern matching, records, more powerful type inference and generic constraints.Over the years C# has been implementing these features too, which is good, but they have been implementing them in incompatible ways, which isn't very good. Since the investment

I saw someone quip (on twitter, I think) many years ago something like:"A junior engineer writes comments that explain what the code does. A mid-level engineer writes comments that explain why the code does what it does. A senior engineer writes comments that explain why the code isn't written in another way." (except punchier, of course. I'm not doing the quip justice here) > writes comments that

People need operations staff, people don't like operations staff and keep trying to treat them like developers.But, operations staff do and have always developed software, just internal software for glue or orchestration, and they work differently to regular software developers in that their customers are usually themselves to meet an internal objective of reliability, stability or ease-of-use for

I grew up seeing founder mode first-hand. My dad founded Celestron, and he operated just as Paul is describing. At my current company, I see the CEO doing the exact same thing, which gives me great hope. Huge contrast from my previous start-up, for which I have great anti-hope unfortunately. (Current company is Zap Surgical Systems, with Dr. John Adler as the founder.) I've seen John everywhere, a

<3it's good to see a little person having fun with all this technocrap that us grognards have gotten so bitter about over the years/decades. :) i hope she continues to have a blast! (from the dedication page in SICP:) "I think that it’s extraordinarily important that we in computer science keep fun in computing. When it started out, it was an awful lot of fun. Of course, the paying customers got s

Really excited for this. Once some more time goes by and the most important python libraries update to support no GIL, there is just a tremendous amount of performance that can be automatically unlocked with almost no incremental effort for so many organizations and projects. It's also a good opportunity for new and more actively maintained projects to take market share from older and more establi

I sometimes wonder why we don't see ruby used for shell stuff more often. It inherited most of the good stuff for shell scripting from Perl, and Perl took a lot of it's syntax from sh and sed and awk, so almost anything you can do in shell script you can do in ruby, but with an option of making it gradually less terse and more readable, while having sane variables and data handling from the start.

That's a good article. He's right about many things.I've been writing a metaverse client in Rust for several years now. Works with Second Life and Open Simulator servers. Here's some video.[1] It's about 45,000 lines of safe Rust. Notes: * There are very few people doing serious 3D game work in Rust. There's Veloren, and my stuff, and maybe a few others. No big, popular titles. I'd expected some A