What's New in Haiku development
The Haiku source is continually built and released for testing purposes nearly every day. You can download and install these latest snapshots to check out the latest features and bug-fixes.
Be aware that nightly images may be unstable. Additionally, some packages included with official releases need to be installed separately.
If you're OK with this, you can find further instructions at our Nightly image page.
TLDR: pkgman install nodejs
As some have already known for a long time, many platforms have had support for writing software in JavaScript or TypeScript with the help of the Node.js runtime and over the years, much of the software written by developers these days have gradually been written in either of those languages. However, Haiku has lacked a Node.js port for quite sometime and it wasn’t possible to run or develop JavaScript based software or libraries that depended on the Node.
Hi there, it's time for the monthly report again! This report covers hrev53338-hrev53461. It's been a busy month!
User interface Andrew Lindesay continue his work on HaikuDepot, tweaking the BarberPole look, adding a display of "usage conditions" (EULA, license, etc) from packages, Ryan Leavengood also worked in this area, making sure if you open an existing hpkg file with HaikuDepot, it will offer you to uninstall the package if it's currently installed.
Introduction Hey there beautiful person reading this post. We are in the endgame now (Ha get it avengers reference!). Yes, Google summer of code 2019 is coming to an end. Phew couldn’t say how 3 months passed by, but this is one of my most memorable experiences I will never forget. So let me wrap GSOC with this final report. Buckle up tight it’s going to be a long post…
Welcome to the monthly report for July 2019! Most of the more interesting changes this month have been from myself in the way of performance optimizations, so I’m writing the progress report this month so I can talk about those in some detail.
This report covers hrev53238-hrev53337 (158 commits.)
Optimizations! Now that Haiku has entered the beta phase, and after the work over the past year or so spent fixing the majority of known kernel crashes and other general instabilities, it is high time we start paying more attention to the whole system’s performance.
PVS studio has just published a series of 3 articles looking over errors and bugs they identified in our sourcecode. PVS is a code static analysis tool that identifies code likely to be incorrect.
They had already run a similar scan back in 2015. At the time, their tools ran on Windows only which had made this quite a challenge for them. They are now more Linux friendly, so it was much easier for them to perform the scan.
Introduction Hello everybody. Sorry for not able to post something for very long time! Previous week was pretty rough for me. So let me tell few things about the state of the port.
We have working IPC (using BMessages)
We have working Minibrowser (that could handle few call back events like navigating to url, going back and forward..)
A partially working network process
Current Work So we decided to get the rendering done.
Hello everybody! It’s been a while since my previous post.
This post is a short summary of all work done upto this point.
During the past few weeks, I was able to add the following features to the current btrfs implementation
Creating new files The basic algorithm behind creating new files is allocating a new inode, updating the fs tree to reflect this, creating a hard link in the directory containing the file and finally updating the cache.
Hey, it's time for a new monthly report already! This one is a bit shorter than usual as the previous one was a bit late, but let's try to get mostly back on schedule. This report covers hrev53175-hrev53238.
Optimizations We are now in beta phase, and besides the usual bugfixes, it's time to start investigating performance bottlenecks in Haiku. Waddlesplash has been hard at work in that area this month, starting with tuning of the newly integrated rpmalloc allocator.
Report for Coding Week #2 and #3 Love that your beautiful face is reading my Blog today❤️. First all I woul like to ask sorry to my fans (if any 😅😂) for delaying the posts. Prepare to get blown away🎉🎉💻
Ok let's all jump into the world of webkit shall we?
History is awesome (just kidding 😉😉) Lets rewind a bit! Getting stuff to compile and build (painful but totally worth it) Oh ya not to mention :making friends!
Hello everybody! It’s been a while since my previous post.
This post is a short summary of all the work done upto this point. For a detailed report of every day, visit this blog I set up using Blogger.
Week 1 As mentioned in my proposal, the target for week #1 was document the current btrfs implementation. As part of this, I documented the following classes * Chunk * Inode * BTree * Attribute * AttributeIterator * DirectoryIterator
