Mainboard VS ruby

[2] https://github.com/FrameworkComputer/Mainboard/tree/main/Mec...

For what it's worth, it is possible to desolder the old connector and solder on a new one. Per Framework's documentation, the connector is a AUSB0534-P203A61. While I was able to find the part on the manufacturer's website, I'm not sure of a way to order it as an individual (I couldn't find it on Digi-Key or Mouser for example).

Maybe in their repo you will find useful numbers: https://github.com/FrameworkComputer/Mainboard

Might be on the pricier side, but the Framework laptop mainboard is available separately starting at $350 https://frame.work/products/mainboard as well as the battery https://frame.work/products/battery, and there's documentation with suggestions/designs on how to built around it for projects like this https://github.com/FrameworkComputer/Mainboard. Should have plenty of power for emulation and light pc gaming, as well as thunderbolt support for an egpu.

Look like trackpad (TP?) is just IIC. https://github.com/FrameworkComputer/Mainboard/blob/main/Electrical/Mainboard_Interfaces_Schematic_11th_Gen.pdf

We released a 3D printable Mainboard Case, and open sourced our Mainboard drawings and electrical documentation in a Github repository.

The block diagram for the Tiger Lake mainboards says that the current displays and motherboards communicate over eDP 1.2 (is Alder Lake-P the same?), so I started by looking for 17.3" screens that communicate with eDP 1.2.

One thing worth noting is that basically, even now (almost 10 months post announcement), almost no one has a 6000U laptop outs (a search on Amazon and Best Buy shows two 6800U laptop models total, one Asus and one Lenovo). Two niche vendors, XMG and Star Labs, have both publicly stated that they would have loved to have offered Ryzen 6000 laptops, but couldn't get any allotments. There are were also well documented chipset issues - even into the summer Lenovo and Asus talked about requiring firmware updates to enable their USB4 ports.

That being said, starting w/ Rembrandt, AMD now has full 40Gbps USB4 controllers built on-chip. I'm really looking forward to Ryzen 7040 because Phoenix looks great (Zen4 + RDNA3 on TSMC N4 - yes please) and hopefully USB4 support has matured enough on the AMD side that Framework is able to release something.

My understanding is that the I/O limitation is in the re-timers - currently the Framework uses 4X JHL8040R's (labeled as Burnside Bridge) directly connected to the iTBT: https://github.com/FrameworkComputer/Mainboard/blob/main/Ele... Apple used these for their first M1 MBAs as well: https://github.com/ThomasKaiser/Knowledge/blob/master/articl...

But both Apple and AMD are now using Kandou retimers:

* https://www.gizchina.com/2022/07/25/apple-completely-got-rid...

* https://kandou.com/matterhorn.html

* https://kandou.com/assets/downloads/product-briefs/KB8001-Pr...

To create a new Rails app, you should have Ruby and Rails installed on your machine. You can find how to install Ruby on your local machine using the Ruby docs. You can install Rails by running the following command:

Ruby testing with RSpec

Not parent poster and do not have production YJIT experience. =)

My guess is that you would monitor `RubyVM::YJIT.runtime_stats[:code_region_size]` and/or `RubyVM::YJIT.runtime_stats[:code_gc_count]` so that you can get a feel for a reasonable value for your application, as well as know whether or not the "code GC" is running frequently.

https://github.com/ruby/ruby/blob/master/doc/yjit/yjit.md#pe...

Link to the commit

Part of the major userbase pull in GitHub revolves around hosting a considerable number of popular projects including Angular, React, Kubernetes, cpython, Ruby, tensorflow, and well even the software that powers this site Forem.

Hold option and click on the “collapse file” button in the Files view of a commit or pull request, and it will collapse all the files.

Select text in a comment, issue, or pull request description and press r—the selected text (including markdown formatting) will get pre-populated as a markdown block quote reply in the next comment box.

Add .patch or .diff to any pull request URL if you want to see a plain-text diff of the pull request (e.g. maybe you want to quickly `curl ... | git apply -` an unmerged pull request into a local copy of the repo without trying to add and fetch the git remote that the pull request is from).

There are lots of keyboard shortcuts. For example, / to jump to the file finder.

Not so much a secret but more like a hiding in plain sight: when looking at a commit GitHub will show you the earliest and latest tag (i.e. release) that includes the commit. For example, this commit[1] first appeared in v3_2_0_preview3.

[1]: https://github.com/ruby/ruby/commit/892f350a7db4d2cc99c5061d...

The title is misleading, just like other commenters mentioned. Just check how much indirection "rb_iv_get()" has to make (at the end, it will call [1], which isn't "a light" call). Now, check generated JIT code (in a blog post) for the same action where JIT knows how to shave off unnecessary indirection.

We are comparing apples and oranges here.

[1] https://github.com/ruby/ruby/blob/b635a66e957e4dd3fed83ef1d7...

I'm not sure why, but all the source values are listed here: https://github.com/ruby/ruby/blob/1cc700907d3ad3368272488a6f...

Maybe someone knowledgeable in the underpinnings of Ruby will explain why "class variable" was not hyphenated.