You could include other major events, such as stock splits or even product launches, that were followed by explosive growth.
789 karma · joined March 12, 2011
More broadly, how are you contributing to the upstream projects?
[1] https://github.com/grafana/loki/issues?page=7&q=is%3Aissue+i...
Also, is there any work on kernel level x86 emulation on arm for expansion roms?
It looks empty because there's no README.md and you could mention it's using Iced as it's ui library.
I would also love to see this for docker/containers, possibly using Spice instead of RDP.
Is Weston GPL? Will Microsoft be contributing these changes under the upstream license?
Also, interesting to see FreeRDP used instead of a Microsoft implementation, since there's already an Android port of it.
This also enabled those users to spend time in MacOS or switch to virtualizing Windows and may lead to one or more personal purchases for themselves or members of their household.
It's a little confusing still why they sold the whole thing while the market was growing.
Marvell seemingly abandoned portable devices and rolled IXP(?) into their own lines for a time.
It's possible to implement GObject subclasses in Rust which little additional overhead as compared to doing it in C, but you get the syntactical niceties of for each loops, traits, and other features of Rust.
librsvg makes good use of these bindings, and is undergoing a rewrite in Rust. Gstreamer bindings are also becoming more complete, and example implementations of many of the standard plugins have been rewritten. The official implementation is still in C though.
Vala is a neat concept though and a pretty clean language.
https://people.gnome.org/~federico/blog/librsvg-gobject-in-r...
COM and OLE, which is based on COM, have been a core part of the Windows shell since at least Windows 95/NT 4.0/IE 4.
You can see this in the registry where shell extensions are simply registered OLE Components, using OLE Activation to to register themselves as toolbars, folder views, context menus and additional commands in context menus.
If you are referring to drivers or core OS concepts at a lower level, you may be right, but DirectX and class drivers were already using COM in places before Vista.
COM is a standard vtable implementing a single core interface, called IUnknown which provides a method of reference counting as well as a way to look up implementaions of specific other interfaces from a given pointer. These interfaces dervive from that base, so they can always be cast as IUnknown.
The rest builds on this base.
source: Inside OLE and Inside Windows 95
https://books.google.com/books/about/Inside_OLE.html?id=adpw...
https://www.bookdepository.com/Inside-Windows-95-Deluxe-Edit...
Edit: saw the reply below, the specific Longhorn components only expanded the scope of what is extensible to include searchable/virtual/indexed filesystem extensions and few other places, based on the innovative concepts in Longhorn. My reading of your comment originally was that Vista was a departure from what came before, though it appears that it may have been intended to say it was more of a return to the simpler COM.
Normally this would also imply an Intel isa, which dictated a multi-component chipset. (North bridge/South bridge) this in turn implies an multi-voltage power supply with a standard plug or plugs derived from the one in the PC AT.
The PC ecosystem also features a set of peripherals, such as floppy drives, hard drives, and CD-ROM drives. These peripherals have their own busses, starting with MFM, and now IDE and SATA. In some cases SCSI entered into the mix, but most consumer-oriented PCs did not use it. These drives were also were powered by the same power supply as the rest of the PC, with an evolving set of connectors and electrical standards.
The Mac took a parallel course, but featured it's own set of proprietary connectors and buses, as well as SCSI, for years before converging with the PC ecosystem in part in later years.
Many of these de-facto and cloned standards were adopted by standards organizations, such as EIA/TIA and IEEE. They were joined by PCI buses, which were used in a diverse set of architectures, including Sun. Later serial variants were developed for the PC and Mac ecosystems, driven by demand for faster graphics accelerators, with a side jaunt to AGP.
At the same time, emdedded devices evolved around a simpler usually single-chip chipset, and often single voltage board designs, with the exception of the cpu core voltage in some cases. These largely used memory-mapped IO with periphrial chips coupled to the memory bus, as well as slower buses such as I2C and SPI. These devices were usually power constrained, having quickly moved into the mobile realm with early PDAs such as the Newton. They mostly developed around the ARM chip which so low power in the early versions that it could run without voltage on it's primary bus.
As the PC ecosystem has evolved, it is now largely built around the PCI bus. PCI is cpu agnostic, so the CPU can be replaced with a different isa while keeping the rest of the system intact.
The PC is also historically modular, so substitutions such as those you suggested can generally be made while keeung the PC nature of the system. M.2 is a modern bus that has veen adopted into the ecosystem primarily for laptops, though also featured in some desktops.
Modern emedded devices are begininning to feature PCI interfaces, though these are only recently appearing in consumer electronics. They have been used in storage-centric chipsets for much longer.
The PC also implies a modular memory bus, with chips or modules complying with a logical and electrical standard, and identifying chip that can be probed by the chipset. In some cases the modularity is reduced and the chips are soldered to the mainboard.
PCs have also begun to adopt single-chip chipsets and System-on-Chip designs, starting with some emdedded intel designs used in mobile tablets and the UMPC. These brought the classic north bridge and south bridge as well as graphics (in this case PowerVR coming from the emdedded world). AMD64 chips also began to include the memory controller on die, leading up to the mentioned APUs that can be powered with the help of a standard embedded power IC from a single low voltage source.
The Linux Core Kernel Commentary [1]
It takes only the parts of the kernel you need to understand, leaving out the drivers, device classes, and much of te ancillary pieces. For the parts it chooses, it goes through them line by line and follows the boot process, explains the concepts of a Unix and SYSV-like kernel.
The 15M lines becomes much less intractible.
[1] https://books.google.com/books/about/Linux_Core_Kernel_Comme...
The New York Times ad was paid for through donations to present an alternative to the closed ecosystem dominated by one browser that didn't follow open standards.
https://blog.mozilla.org/blog/2017/11/14/fast-for-good-launc...
Early versions of Firefox featured links to various news organizations and stories pulled from their feeds, until certain jurisdictions threatened to block the browser entirely.
At some point their missions may have diverged, but the marketing of both were closely intertwined. MoFo accepted donations and other sources of funds which it used, in part, to fund development of a browser by MoCo. Other projects came later, but the community's understanding of their respective roles remained the same.
As a long-term observer I followed this closely when the Foundation and Commercial split was announced, and remember reassurance s about the core mission being loudly proclaimed.
Here it is from the former CLW herself:
https://blog.mozilla.org/blog/2007/08/09/firefox-is-a-public...
I have run Mobian and Phosh on Pinephone and while clean it was slow, clumsy to switch apps, and did not size most apps properly.
Is it possible to manually configure the port to work with HDMI or as a host (in sysfs), or is the hardware change required (on preorder/braveheart phone)?
Is there a single place with the most up-to-date kernel sources with usb hardware drivers, audio support for modem, etc.?
At the time, netbooks were growing organically and could be had with 2 or 4 gigabytes un some cases, with Linux for less that the Windows version.
Microsoft countered this with cheaper versions of Windows that were limited to lower specs, such as 2 gb.
This was the so-called "starter edition" of XP and similar licensing programs for Vista.
The policies might have changed with Windows 10 (not sure), but the legacy remains.
At the same time, companies were locking down WScript due to scripting viruses and HTAs that were impersonating other applications with their configrable icons.
* server side WASM such as cloudflare workers and kv to build and maintain the index
* streaming copy of the simplified index to be pulled in by a browser-side wasm
* queries that go beyond the simple index forwarded to the worker
One way of simplifying would be to limit search terms to a certain length, or only expose the most popular results.
By sharing wasm code the format can be optimized and not require a compatibility layer or serdes.