The codec directory was an idea that I think they got from AmigaOS' "Datatypes" mechanism. I remember that Amiga was the first platform where all* web browsers would support PNG, because someone had written a PNG datatype and released it as free software.
*: Yeah, yeah, Lynx did not technically view images, but it could download an image and launch an external image viewer... which would usually support datatypes.
I think that what a smartwatch needs to be is as a "companion device" to a phone, and nothing more. It needs a screen, two buttons (or areas to tap) for "Yes" and "No" and low-bandwidth communication with the phone. The phone tells the watch what to display and what the buttons mean. The watch then needs only to reply with "Message understood, displaying screen", "Yes" and "No". That's it. All the "killer apps" that a smartwatch could be used for require those things and nothing more.
The Samsung watch and many stand-alone smartwatches are too powerful, too feature-rich and already too bloated. The Samsung watch is already too large to wear comfortably on the wrist. Has anyone mentioned battery life yet? My Casio has a battery life measured in years.
... and in Bob Kane's original Batman comics, first printed in Detective Comics #31 in 1939, Batman did not use a "batplate" or a "batcopter". He used a "batgyro". The first "batarang" was introduced in the same panel.
That shortcut opens a new Incognito window in Chrome, also called "Private browsing" in Firefox.
Also very useful. Incognito windows lets me can log into my gmail account without having to log out of Youtube... and when the incognito windows are closed, I am automatically logged out of gmail.
I agree with most of your points, but it is a bit late now...
If I had been Microsoft, I would have leveraged the "Metro" name instead: Windows Phone -> Metro Phone, Windows RT -> Metro Tablet, but let full-featured (x86) tablets remain Windows tablets. Then, instead of letting the desktop be an "app", expand on the tiling windows of Windows 7 and place Metro apps in tiled windows on the desktop. Also, add multiple workspaces to Windows desktop -- it is about effing time.
Sorry, but multicore does not scale that well. As soon as one core needs data that is not in the cache, it stalls. A stalled core is a core that does not run. The best utilization of multicore is if you are using all cores on the same problem, and the same data. Making your code scale to multiple cores can be quite tricky. I found that [url=http://channel9.msdn.com/Events/Build/2013/4-329]this talk at Microsoft Build 2013[/url] explains quite well what you need to do.
The X41 had only a swiveling screen, pen and a couple of physical buttons on top. It did not come apart into two parts.
The two laptops serve different users. You could say that the X41 is primarily a laptop and a tablet secondarily, while the Helix is primarily a tablet and a laptop secondarily. The tablet is easier to carry, and might therefore be preferable if you are going away/travelling and you don't think that you will be typing much. The X41 is when you do mostly traditional computing and you need tablet functionality only sparingly.
The X41 had a dock also, for desktop use. I would like to see a (vertical) desktop dock for the Helix tablet so that I can use it with a desktop screen and keyboard, and without having to connect the keyboard part first.
Yet, practically all types of medicinal pills still contain nanoparticles of Titanium Dioxide, used only for colouring the pills white. It is not like you have the option of choosing another brand that does not have nanoparticles. Often the prescribed medicine is the only one available with the active ingredient... or all the brands contain TiO2. TiO2 is also in many brands of sunscreen, but in this case it is much easier to choose another brand.
Precisely. I mentioned accounting for false positives, and batkiwi's algorithm does not do that. In a textbook example, you should have a delay on rising edge and "stickiness" on the falling edge, but sometimes you can take shortcuts.
I have studied several firmwares for actual computer keyboards, which all work as I described. You may want to trigger directly on the rising edge if you have another type of application where your scanning rate is quite low.
The scanning frequency is not that significant. The response time is more limited by something called "debouncing".
When a key switch is pressed, it does not actually change state from open to closed in a perfect way. Instead, it often "bounces" between open and closed states for a little while until it settles. Another issue is that short spurious positives may be caused by static electricity. Keyboard microcontrollers will therefore have to delay reporting each key press until it is sure that the key reports a steady state. Debouncing is almost always implemented as a counter or a buffer with a delay - and that delay is fixed. The delay is chosen based on the characteristics of the particular keyboard switch.
By increasing the scanning rate, the microcontroller will only gather more samples for debouncing each key. As you increase the scanning rate, your response time will only approach the debouncing delay; It will never surpass it.
Why not fork GTK+ 2.0 and keep maintaining the fork? That would keep the Lightweight XDesktop Environment being a lightweight desktop environment for X...
They episodes are already together called the [url=http://starwars.wikia.com/wiki/Journal_of_the_Whills]Journal of the Whills[/url]. This is found in early "drafts" of George Lucas' Star Wars scripts from the '70s and has since then become included in Star Wars novels.
At least, within the European Union, regular bank transfers are free (to a certain extent). But then, governments (and in some cases, banks) can freeze bank accounts.
This topic reminds me of the Georgia Guidestones. They are a monument of granite stones that contain ten simple "guidelines" for future civilisations. The guidelines are repeated in eight different languages: each language having a face of each of the four main stones.
The diagonal means something different depending on which aspect the screen has. We have 16:9, 16:10, 3:2 (Chromebok pixel) and 4:3, and now 2.37:1 and the angle of the diagonal is different on all of them. How about using a metric that does not change, such as.. maybe the height of the screen. This "29 inch screen" is only as large on the vertical as a 23 inch diagonal 16:9 screen. Both are 11" high.
I also feel the need for this. I think that the browser could also have a "personality" linked to each bookmark, so that it would switch personality automatically when I choose to go a specific site.
The current 7th gen iPod Nano that came last year is too big to use as a watch. Lots of people are using the 6th gen iPod Nano as a watch, but it doesn't have any features that a true "smartwatch" should have and you can't install apps on it.
Personally, I think that a smartwatch should be designed as a "dumb" terminal to a smartphone, although maybe with an interactive display so that you could move between pages of notifications/time/calendar from different apps. In other words, it should be an accessory to the phone. You should only need to install apps on the phone and those apps would push data to the watch whenever there is an update. Such a smartwatch would have a low-power screen and would sleep most of the time to conserve battery. The iPod Nano can't do that.
I don't understand people who want to gulp down gallons of soda while they watch movies. Your bladder gets full and you have to either sit there for two hours in discomfort or scuffle out to get to the bathroom to relieve yourself having inconvenienced half the row on your way out.
If I want to eat candy at the movies, I bring my own. The selection is not always that good at the theatre, and the prices are horrible.
Actually, FLAC is technically similar to MP3 in a sense. It consists of an inherently lossy encoding in the frequency domain (like MP3) plus an encoding of the difference between the lossily encoded audio and the original. The first part is a bit more straightforward than MP3 because it does not do any tricks adapted to the human ear.
From what I have hard, the Lego model makers use solvent to chemically weld the pieces together.
When they can get a legal permit, they use GBL -- which unfortunately would turn into the drug GHB when you add water. Otherwise they use MEK. GBL is believed by Lego to be less toxic than MEK. (Well.. you are not supposed to drink either, so this is about skin contact and fumes.)
Slashdot Mirror
The codec directory was an idea that I think they got from AmigaOS' "Datatypes" mechanism.
I remember that Amiga was the first platform where all* web browsers would support PNG, because someone had written a PNG datatype and released it as free software.
*: Yeah, yeah, Lynx did not technically view images, but it could download an image and launch an external image viewer ... which would usually support datatypes.
I think that what a smartwatch needs to be is as a "companion device" to a phone, and nothing more.
It needs a screen, two buttons (or areas to tap) for "Yes" and "No" and low-bandwidth communication with the phone. The phone tells the watch what to display and what the buttons mean. The watch then needs only to reply with "Message understood, displaying screen", "Yes" and "No". That's it.
All the "killer apps" that a smartwatch could be used for require those things and nothing more.
The Samsung watch and many stand-alone smartwatches are too powerful, too feature-rich and already too bloated. The Samsung watch is already too large to wear comfortably on the wrist. Has anyone mentioned battery life yet? My Casio has a battery life measured in years.
... and in Bob Kane's original Batman comics, first printed in Detective Comics #31 in 1939, Batman did not use a "batplate" or a "batcopter". He used a "batgyro". The first "batarang" was introduced in the same panel.
Precisely. Isn't this the real issue here that the trademark "Ministry of Sound" is being used for playlists on Spotify.
That shortcut opens a new Incognito window in Chrome, also called "Private browsing" in Firefox.
Also very useful. Incognito windows lets me can log into my gmail account without having to log out of Youtube ... and when the incognito windows are closed, I am automatically logged out of gmail.
I agree with most of your points, but it is a bit late now...
If I had been Microsoft, I would have leveraged the "Metro" name instead: Windows Phone -> Metro Phone, Windows RT -> Metro Tablet, but let full-featured (x86) tablets remain Windows tablets.
Then, instead of letting the desktop be an "app", expand on the tiling windows of Windows 7 and place Metro apps in tiled windows on the desktop. Also, add multiple workspaces to Windows desktop -- it is about effing time.
Sorry, but multicore does not scale that well.
As soon as one core needs data that is not in the cache, it stalls. A stalled core is a core that does not run.
The best utilization of multicore is if you are using all cores on the same problem, and the same data. Making your code scale to multiple cores can be quite tricky. I found that [url=http://channel9.msdn.com/Events/Build/2013/4-329]this talk at Microsoft Build 2013[/url] explains quite well what you need to do.
Yes, but MediaTek is who is claiming that its CPU with eight equal cores is better than 4+4 big.LITTLE.
Qualcomm is saying "No, it's not".
The X41 had only a swiveling screen, pen and a couple of physical buttons on top. It did not come apart into two parts.
The two laptops serve different users. You could say that the X41 is primarily a laptop and a tablet secondarily, while the Helix is primarily a tablet and a laptop secondarily.
The tablet is easier to carry, and might therefore be preferable if you are going away/travelling and you don't think that you will be typing much. The X41 is when you do mostly traditional computing and you need tablet functionality only sparingly.
The X41 had a dock also, for desktop use. I would like to see a (vertical) desktop dock for the Helix tablet so that I can use it with a desktop screen and keyboard, and without having to connect the keyboard part first.
They could rebrand them, reinstall the OS on them and sell them as Android tablets. ...
People want those apparently
Yet, practically all types of medicinal pills still contain nanoparticles of Titanium Dioxide, used only for colouring the pills white. ... or all the brands contain TiO2.
It is not like you have the option of choosing another brand that does not have nanoparticles. Often the prescribed medicine is the only one available with the active ingredient
TiO2 is also in many brands of sunscreen, but in this case it is much easier to choose another brand.
Precisely. I mentioned accounting for false positives, and batkiwi's algorithm does not do that. In a textbook example, you should have a delay on rising edge and "stickiness" on the falling edge, but sometimes you can take shortcuts.
I have studied several firmwares for actual computer keyboards, which all work as I described. You may want to trigger directly on the rising edge if you have another type of application where your scanning rate is quite low.
The scanning frequency is not that significant. The response time is more limited by something called "debouncing".
When a key switch is pressed, it does not actually change state from open to closed in a perfect way. Instead, it often "bounces" between open and closed states for a little while until it settles. Another issue is that short spurious positives may be caused by static electricity. Keyboard microcontrollers will therefore have to delay reporting each key press until it is sure that the key reports a steady state.
Debouncing is almost always implemented as a counter or a buffer with a delay - and that delay is fixed. The delay is chosen based on the characteristics of the particular keyboard switch.
By increasing the scanning rate, the microcontroller will only gather more samples for debouncing each key. As you increase the scanning rate, your response time will only approach the debouncing delay; It will never surpass it.
Why not fork GTK+ 2.0 and keep maintaining the fork? ...
That would keep the Lightweight X Desktop Environment being a lightweight desktop environment for X
They episodes are already together called the [url=http://starwars.wikia.com/wiki/Journal_of_the_Whills]Journal of the Whills[/url].
This is found in early "drafts" of George Lucas' Star Wars scripts from the '70s and has since then become included in Star Wars novels.
At least, within the European Union, regular bank transfers are free (to a certain extent).
But then, governments (and in some cases, banks) can freeze bank accounts.
This topic reminds me of the Georgia Guidestones.
They are a monument of granite stones that contain ten simple "guidelines" for future civilisations.
The guidelines are repeated in eight different languages: each language having a face of each of the four main stones.
The diagonal means something different depending on which aspect the screen has. We have 16:9, 16:10, 3:2 (Chromebok pixel) and 4:3, and now 2.37:1 and the angle of the diagonal is different on all of them. .. maybe the height of the screen.
How about using a metric that does not change, such as
This "29 inch screen" is only as large on the vertical as a 23 inch diagonal 16:9 screen. Both are 11" high.
I also feel the need for this.
I think that the browser could also have a "personality" linked to each bookmark, so that it would switch personality automatically when I choose to go a specific site.
The current 7th gen iPod Nano that came last year is too big to use as a watch.
Lots of people are using the 6th gen iPod Nano as a watch, but it doesn't have any features that a true "smartwatch" should have and you can't install apps on it.
Personally, I think that a smartwatch should be designed as a "dumb" terminal to a smartphone, although maybe with an interactive display so that you could move between pages of notifications/time/calendar from different apps.
In other words, it should be an accessory to the phone. You should only need to install apps on the phone and those apps would push data to the watch whenever there is an update.
Such a smartwatch would have a low-power screen and would sleep most of the time to conserve battery. The iPod Nano can't do that.
I don't understand people who want to gulp down gallons of soda while they watch movies.
Your bladder gets full and you have to either sit there for two hours in discomfort or scuffle out to get to the bathroom to relieve yourself having inconvenienced half the row on your way out.
If I want to eat candy at the movies, I bring my own. The selection is not always that good at the theatre, and the prices are horrible.
Actually, FLAC is technically similar to MP3 in a sense.
It consists of an inherently lossy encoding in the frequency domain (like MP3) plus an encoding of the difference between the lossily encoded audio and the original. The first part is a bit more straightforward than MP3 because it does not do any tricks adapted to the human ear.
We need to get an International treaty in place against these kinds of weapons before everyone has their own.
It is made from large Lego bricks ... made from Lego bricks.
I also thought that the picture in the article was photoshopped, until I saw close-up pictures of each "brick" being jagged.
From what I have hard, the Lego model makers use solvent to chemically weld the pieces together.
When they can get a legal permit, they use GBL -- which unfortunately would turn into the drug GHB when you add water. Otherwise they use MEK. GBL is believed by Lego to be less toxic than MEK. (Well.. you are not supposed to drink either, so this is about skin contact and fumes.)