Great progress! Congrats MS for breaking their dependency on Intel stack & pipeline. I also loved that 20% of the plastics was harvested from the ocean trash plastics.. Hope that percentage will increase more in the future..

I own it and a Snapdragon Lenovo Miix 630. Both can hit 100% and Windows does NOT freeze like a Intel chip. Never going back folks.

Cool 🎉

this is a dumb question. lol maybe it's for chatgpt. If you build for ARM does that have any implication for linux versus windows? IoT devices are mostly on Linux so what tie in would this have for let's say developing on windows or windows server ARM to IOT on linux? Any portability there or am I just off into left field?

@christian15213

9 ай бұрын

Your question is not dumb at all! It's actually quite relevant, especially in the context of modern software development. Let's break down your question step by step: Building for ARM: Building for ARM architecture involves compiling software to run on processors that are based on the ARM instruction set. ARM architecture is commonly found in a variety of devices, including IoT devices, smartphones, tablets, and more. Linux vs. Windows: The choice of operating system (OS) depends on the specific requirements of your project. Linux is popular for IoT devices due to its lightweight nature, open-source nature, and extensive support for various hardware platforms. Windows can also run on ARM devices and has its own set of use cases. Developing on Windows for Linux IoT: You can certainly develop software for Linux-based IoT devices using development tools available on Windows. This is possible through cross-compilation or virtualization. Cross-compilation involves compiling your code on a Windows machine to generate executables that can run on Linux ARM devices. Virtualization allows you to run Linux environments within Windows using tools like WSL (Windows Subsystem for Linux) or virtual machines. Windows Server ARM to Linux IoT: Developing on Windows Server ARM for Linux IoT might not be the most common scenario, but it's possible. It would involve setting up development tools and cross-compilation environments that can target Linux ARM devices. Again, virtualization could be useful here. Portability and Compatibility: While it's technically feasible to develop on Windows for Linux-based ARM devices, you'll need to be mindful of potential compatibility issues. Libraries, dependencies, and system calls might differ between Windows and Linux. Ensuring your code works seamlessly on the target Linux environment will require careful testing and adjustments. In summary, there is a degree of portability when it comes to developing on Windows for Linux IoT devices. However, it's important to consider the differences between the two operating systems, as well as potential challenges related to dependencies and system calls. If you're primarily targeting Linux IoT devices, you might find it more straightforward to develop on a Linux environment or use tools like cross-compilation to ensure smoother compatibility.

@christian15213

9 ай бұрын

Developing for ARM on Windows with the intention of porting over to Linux can have certain advantages and considerations. Let's delve into them: Advantages of Developing for ARM on Windows for Porting to Linux: 1. **Closer Architecture Match:** Developing for ARM on Windows provides a closer architecture match if your target is an ARM-based Linux system. This can potentially reduce compatibility issues that might arise when transitioning from x86 Windows to ARM Linux. 2. **WSL (Windows Subsystem for Linux):** WSL allows you to run a Linux distribution alongside Windows without the need for virtualization or dual booting. WSL 2, in particular, provides a full Linux kernel, which can facilitate cross-compilation and testing of ARM-specific code. 3. **Testing in a Controlled Environment:** Developing on Windows can help you build and test your codebase in an environment that you're more familiar with. You can ensure that your application works as intended on Windows before porting it to Linux. 4. **Integrated Development Environment (IDE):** Windows offers a wide range of powerful IDEs and development tools that you might be accustomed to. This can make the development process more comfortable and efficient. 5. **Gradual Transition:** If you're already experienced with Windows development tools and environments, using them to target ARM can provide a smoother transition as you begin to develop for Linux ARM. Considerations and Challenges: 1. **Dependencies:** Depending on the libraries and dependencies your project uses, there might be differences between Windows and Linux. You'll need to ensure that the libraries you use are available and compatible on both platforms. 2. **System Calls:** System calls and low-level interactions can differ between Windows and Linux. Code that relies heavily on platform-specific system calls might require adjustments when porting. 3. **Endianness:** ARM processors can support both little-endian and big-endian modes. Ensuring consistency between Windows and Linux regarding endianness is essential. 4. **Performance Differences:** ARM processors on Windows might have different performance characteristics compared to those on Linux due to various factors like kernel optimizations and drivers. 5. **Cross-Compilation Complexity:** Cross-compilation can introduce complexities, especially when dealing with intricate build systems and dependencies. Debugging and testing might be more challenging in this scenario. 6. **Native Linux Development:** If your ultimate goal is to develop software for Linux ARM, consider that native development on a Linux machine might provide a more straightforward and streamlined experience. In conclusion, developing for ARM on Windows with the intention to port over to Linux can offer advantages in terms of familiarity, testing, and development environment. However, you'll need to carefully manage dependencies, system calls, and other platform-specific considerations when transitioning your code to the Linux ARM environment. If your focus is primarily on Linux ARM development, developing directly on a Linux machine might be a simpler approach.

"Fairly new to the market"... yeah, Acorn had machines using it in the late '80s. "Leverages a new instruction set design called RISC"... yeah, the RISC concept has its origins back in the '60s, so maybe not that new? And no, you can't buy a Windows Arm Developer Kit unless you're in a handful of markets -- it's not available in New Zealand

Do you have any benchmarks of running Java on this device?

@jimbobbennett

Жыл бұрын

Sorry - we don't have any Java benchmarks at the moment.

@ABarmin

Жыл бұрын

@@jimbobbennett Thank you for the answer. I suppose Java also should work fine but still thinking how exactly.

@jimbobbennett

Жыл бұрын

@@ABarmin The OpenJDK for Windows has Arm64 support - learn.microsoft.com/java/openjdk/download

Yeah, pretty new architecture, it has only been around since 1985.

@jimbobbennett

Жыл бұрын

New to Windows, not new new hence the discussion about it being the same processor as is in my phone. The rise of Arm in the cloud and desktop is pretty new, only happened over the past few years to a serious degree.

@ReneMalingre

Жыл бұрын

@@jimbobbennett I had a Surface RT in 2012

Is the 2023 Dev Kit leased, or do we get to keep it?

@grappydingus

11 ай бұрын

For keeps according to the KZread video reviews I've seen.

a lot of bugs still breaks the user experiences. Please fix the bugs first.

Made in India, Make in India