Hi,
I am recently having some hard time with Chromium, it has worked for a very long time, now it is unusable.
It is about 2-3 years I am using FreeBSD as my main work system, and I think this is one of the thing that must be improved.
I guess all of you use a Web Browser to work these days. I understand that FreeBSD is mostly a server side OS, but, If we want to have any expectation of anybody deciding to use it on the desktop we must fix the browser issue.
Also, consider, FreeBSD is watching to the embedded world. But in the embedded world things have often a screen and a GUI, this GUI is often a just a web page. What people see of your embedded thingy will be just a screen with a browser window open. So, it is better the browser to work reliably, even if we don't care much about desktop users.
I remember when I started I had some other ugly issues with the browser. Then they were solved and for a while all went fine. Now we are back at the starting point.
I am not the most experienced when it comes to ports and packages but, I want to try to propose a possible solution.
What if we implement a package version of a main browser which is fully-statically-compiled? No dependency on other ports or local libs. The browser will be a big binary containing all its universe.
Then, when times come for a new release of the browser to be released we don't delete the old binary-browser package, we just add the new one. Only on the next-next release the older browser will be removed from the repository. In such a way we will be reasonably sure people never remain without their trusted tool.
bye
n.
I am recently having some hard time with Chromium, it has worked for a very long time, now it is unusable.
It is about 2-3 years I am using FreeBSD as my main work system, and I think this is one of the thing that must be improved.
I guess all of you use a Web Browser to work these days. I understand that FreeBSD is mostly a server side OS, but, If we want to have any expectation of anybody deciding to use it on the desktop we must fix the browser issue.
Also, consider, FreeBSD is watching to the embedded world. But in the embedded world things have often a screen and a GUI, this GUI is often a just a web page. What people see of your embedded thingy will be just a screen with a browser window open. So, it is better the browser to work reliably, even if we don't care much about desktop users.
I remember when I started I had some other ugly issues with the browser. Then they were solved and for a while all went fine. Now we are back at the starting point.
I am not the most experienced when it comes to ports and packages but, I want to try to propose a possible solution.
What if we implement a package version of a main browser which is fully-statically-compiled? No dependency on other ports or local libs. The browser will be a big binary containing all its universe.
Then, when times come for a new release of the browser to be released we don't delete the old binary-browser package, we just add the new one. Only on the next-next release the older browser will be removed from the repository. In such a way we will be reasonably sure people never remain without their trusted tool.
bye
n.